App / Data engineering and quality
Build a data freshness dashboard
Build a freshness App that distinguishes load success from business event recency, compares refresh lag with targets, and flags unknown coverage.
Data analyst · Analytics engineer
Bring this question into Chat
Your starting prompt.
Build one App from [governed datasets] and [ingestion logs] to show source freshness, latest business timestamp, last successful load and refresh lag against [expected cadence]. Distinguish stale business activity from failed ingestion and identify sources blocking [reports]. Include timezone, freshness definitions and evidence links. Display unknown coverage explicitly and prepare an internal review queue for breached thresholds.
Copy this starting point, then replace the placeholders with your own inputs.
Method and review
Keep the assumptions visible.
Profile keys, row counts, types, missing values and join cardinality. Retain source lineage and concrete exception records so a correction can be checked.
For this task, check
A recently loaded dataset can still contain stale business events.
Before you begin
- Bring exports you are allowed to upload, or data your Workspace can already query.
- Choose the reporting period and agree what each record represents.
- Select the data your App can query before building its views.
Build one App from data you have permission to query. Review its definitions and calculations with your team.
Synthetic illustrative example
See the method in practice.
Synthetic input. Illustrative output checked locally; this is not a live Proforma run or customer result. Freshness review at 2026-09-30 12:00 UTC. Ingestion lag threshold is two hours; business activity has a separate definition.
These invented records explain the method. They are not a recorded Proforma run.
| Source | Last successful load UTC | Latest event UTC | Last run |
|---|---|---|---|
| Orders | 30 Sep 11:00 | 30 Sep 10:00 | Success |
| Usage | 30 Sep 05:00 | 30 Sep 11:00 | Failure at 11:30 |
| Invoices | Unknown | Unknown | Failure at 11:00 |
| Source | Load lag | Business event lag | Review state |
|---|---|---|---|
| Orders | 1 hour | 2 hours | Within load threshold |
| Usage | 7 hours | 1 hour | Load threshold breached; inspect failure |
| Invoices | Unknown | Unknown | Coverage unknown; inspect run |
Method
Compute each lag from its own timestamp in UTC. A recent business event is not proof of a successful load; failed-run time is not last-success time. Unknown timestamps are not silently set to now.
What the result tells you
Usage illustrates different ingestion and business timestamps that need source review. These rows preview a freshness App; no Source is refreshed and no monitoring schedule is activated.
Take the next step
Make it your investigation.
Copy the prompt above, create or open your Workspace, and paste it into Chat. Add the inputs you have permission to use and adapt the assumptions with your agent.
Start exploringYour prompt is carried by copy and paste. Signing up does not submit it or start this work automatically.
Or start with your own agent
The setup prompt includes this public task. Your agent will help you connect when needed and use the access you approve.