> ## Documentation Index
> Fetch the complete documentation index at: https://help.autoady.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Check freshness and missing data

> Tell a quiet period apart from a stale report, incomplete coverage, or a failed refresh.

Use the source time and displayed status to decide whether a report is ready for a decision. Opening a page or seeing old rows does not prove that a new provider read succeeded.

## Check in this order

1. Confirm the selected account or customer and the entity level.
2. Check the reporting dates. A quiet period or a restrictive filter can correctly return no rows.
3. Open **Reporting details** where available and read the when data was last fetched, timezone, attribution, and completeness.
4. Use **Refresh** once and inspect the new state. If the refresh fails, read the warning alongside any retained data.
5. Check connection health and permissions if data cannot load. Reconnect only when the error requires it.

## What the states mean

| State | Next step |
| - | - |
| No activity or no rows | Check dates, filters, account selection, and whether the account was actually running ads. |
| Insufficient evidence | Use a meaningful period with enough relevant activity. Do not infer that a recommendation is missing because the app is broken. |
| Stale data or refresh failed | Treat the retained report as an older snapshot; retry the read and check its source time. |
| Partial or incomplete data | Read the coverage warning before using a total as complete. |
| Source time unavailable | The age of the source cannot be confirmed from that view. |
| Permission, connection, or setup error | Resolve the displayed blocker before relying on the report. |

## Keep time concepts separate

Reporting dates describe the activity window. Fetch time describes when the provider was read. Current configuration describes today's status or budget. These can legitimately refer to different times.

Providers can revise attributed results after the initial report. A current-day report is also still accumulating activity. Compare settled, equivalent periods when investigating a trend.

## When to escalate

If a read repeatedly fails after the appropriate reconnect or retry, capture the account ID, period, fetch time or warning, and exact error. For a pending write or purchase, check that original attempt rather than starting a new one to fix a read problem.

Next: [Troubleshooting by symptom](/help/troubleshooting) or [contact support](/help/contact).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.