A page is empty when it should not be
Tell a loading view, an empty result, a failed request, and a metric that cannot be computed apart.
2 min read
Read the message alongside the empty area. A loading state, a successful result without records, a failed request, and an unavailable metric all need different checks. A dash in a KPI leaves the value unspecified. Zero is a recorded numerical result.
Identify the state you are seeing
- If a loading indicator is still present, wait for a result or an error. For an import or a connection job, check its status in the workspace that started it.
- If the page confirms no results, check its account, date range and filters. Open the corresponding list to look for the expected record.
- If the page shows a failed request, use Retry where available. Keep the error message if the same failure returns.
- If only one figure shows a dash, check whether the needed data exists. A win rate needs classified results, and a chart can have no points in its selected period.
When a retry still leaves the page empty
Capture the message and the selected filters. Send the date, the page and one expected record that you can find elsewhere, or include the source import or connection result if the record is missing there too.
Did this article answer your question?