Scan history
The Scans page keeps a chronological record of every run — manual, scheduled, and API-triggered.
What’s recorded
Section titled “What’s recorded”For each run you can see:
- Scan type — cost sync, analysis, waste detection, recommendations, or a full Run All.
- Status — Succeeded, Failed, or Running, with start time and duration.
- Trigger — who or what started it (a user, the schedule, or the API).
- Result summary — what the run produced or why it failed.
Filtering
Section titled “Filtering”Filter the history by scan type, status, and date range to answer questions like “did last night’s refresh succeed?” or “when did waste detection last run for this scope?”
Troubleshooting failed runs
Section titled “Troubleshooting failed runs”- A failure during the pre-flight check means a connection couldn’t authenticate — open Cloud Connections and use Test on the named connection, then re-run.
- Transient cloud API issues typically clear on the next run; persistent failures on one connection point to expired credentials or revoked consent.
- A run that was interrupted (for example by a service restart) is closed out automatically and marked as failed rather than staying “Running” forever.