Commerce OS guide
Data Freshness and Completeness
Check recency and completeness before interpreting a number
Store data arrives on different schedules and may be delayed by Shopify processing, connection changes, permissions or the time needed to complete a measurement window. Freshness explains when a source was last confirmed; completeness explains whether the expected scope is available.
Read a freshness state
- Current
- The source is within its expected update window for the decision being reviewed.
- Delayed
- The latest expected update has not completed; recent activity may be missing.
- Unknown
- Liva 7 cannot confirm a reliable update time or complete source scope.
Investigate in order
- Confirm the metric timeframe and the timestamp of the latest complete source.
- Check whether the Shopify connection and required permissions remain active.
- Look for a known processing, import or service state.
- Compare the affected scope with an older complete period.
- Retry only when the interface indicates that retrying is safe.
Delayed does not mean zero
Do not approve a consequential action from a partial window. Wait, narrow the decision or use an explicitly labelled earlier complete period.