Data Freshness and Processing Status

Understand the difference between connection, inventory, billing and allocation timestamps.

Several timestamps can describe the same workspace: last AWS role validation, last inventory discovery, export execution time, last cost ingestion, last allocation run, recommendation observation time and report generation time. They are not interchangeable.

The data pipeline

Connection validated
   ├── Inventory discovery → resource snapshot
   ├── Cost export produced → cost ingestion → allocation
   └── Recommendation source refreshed → opportunity snapshot

One successful branch does not prove that another branch succeeded. For example, inventory can be current while AWS costs are delayed because the CUR 2.0 export has not finished.

Reading job states

A queued or running job has not yet produced a terminal result. Succeeded means that job completed, but verify coverage and the authoritative output version. Failed or partial results must preserve the previous good financial state rather than silently replacing it with incomplete data.

If your dashboard is empty

First confirm the selected workspace and the existence of source records. Then check Settings/AWS Connections and the job-run history. Review the exact error or missing input: STS trust, export/bucket access, cost period, disabled recommendation source or mapping gap.

Reports and evidence

A report may be generated at noon from data ingested earlier. Always distinguish generated at, source observed at and financial period. Displaying these separately builds confidence with finance and audit stakeholders.