How should a data-heavy dashboard communicate delayed data?

Hi Product Hunt!

I’m building Gold Dashboard, a research-first XAUUSD dashboard at TR-MATE.

One product-design problem I keep coming back to is what a dashboard should show when one of its data sources is late or temporarily unavailable.

Prices, chart history, news, and market analysis do not update at the same speed. Treating every section as either “live” or “broken” makes the interface harder to trust, so I’m working with more explicit states:

• Fresh data when the latest update arrives on time

• Cached data when the last validated result is still useful

• Delayed data when the source is reachable but has not updated

• Unavailable data when there is nothing safe to display

The current design also tries to keep the last readable content visible instead of clearing the entire page because one API request failed. A news request should not remove a working price chart.

I’d love to hear from people who build or use data-heavy products:

1. Would you rather see cached data with a clear timestamp, or an empty state until fresh data arrives?

2. How much detail should an error message show on the main screen?

3. Which makes a dashboard feel more trustworthy: update timestamps, source labels, status badges, or something else?

You can see the current interface here:

https://copi-tools.com/gold-dashboard/

I’m interested in the information-design and user-trust side of this problem, not trading predictions or financial advice.