Pre-computed dashboard FAQ

Last updated 10/03/2026

FAQ

What is the base date of a dashboard?

Reports in AE usually define a query Time Range. When a relative date such as today, yesterday, 3 days ago, or last week is used, AE calculates the specific time range of that relative date based on the Base Date. For example, if a report is defined as "today's revenue" and the dashboard's base date is July 1, the report data shown on the dashboard is "revenue on July 1". The dashboard's base date requires all reports on the dashboard that define a relative time range to calculate their time range from this date. If a report uses static dates, such as May 1 to May 7, the dashboard's base date doesn't affect the report's time range.

How do I view the base date of a dashboard?

When the base date isn't Today, the specific base date is shown. The base date is the date in the dashboard's current time zone.

Why does a dashboard with pre-computation still compute when I open it?

A pre-computed dashboard is computed with the default conditions only at the scheduled time. If the conditions don't match, the pre-computed results can't be used. You can troubleshoot from the following aspects:

Aspect	Description
Pre-computation not started	The first pre-computation start time hasn't arrived yet, so no pre-computed results are available
Pre-computation failed	Check the task status in "Pre-computation Task Log". There are several cases: The status is "Queued": pre-computation was delayed, so the previous results can no longer be used (currently the previous data is kept for at most 1 hour after the scheduled execution time of this run; if the delay is longer, the previous cache can't be hit) Some reports failed during pre-computation. If a failed report still fails after retries, an ad hoc calculation starts when you open the dashboard. This is usually a performance issue; try running it outside peak hours first. If it still fails, contact the ThinkingAI R&D team with the error code in "Description" to locate the cause together.
Data permissions	Check your data permissions in "Personal Center" and compare them with the data permissions of the dashboard creator. If they differ, the pre-computed results can't be used. Even with the same data permission, if its definition at pre-computation time differs from its definition at viewing time, the pre-computed results can't be used either.
Time zone	Compare the pre-computation time zone in "Dashboard Settings" with the current time zone of the dashboard. If they differ, the pre-computed results can't be used. If the dashboard's default time zone was changed after pre-computation completed, the pre-computed results can't be used
Default filter conditions	Are personal default filter conditions in use? When the personal default filter conditions differ from the global default filter conditions, the pre-computed results can't be used.
Filter conditions	Are the current page filter and space filter the same as their default values?
Fixed date range	Is the current global date range the same as the fixed time range set for the dashboard?
Report definition changes	This may be caused by report changes or changes to dashboard report settings: Definition changes can be viewed in the report change log Report setting changes can't currently be located through the UI, but you can recall whether any of the following changed: 1. Chart type1. Time range1. Time granularity1. Stage value/comparison value settings
New reports	Reports added to the dashboard after pre-computation have no pre-computed results available and may trigger ad hoc queries