Skip to main content
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

​
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 or contact support.