Data delays

Overview

Cost data in Cost Analyzer reflects what Azure Cost Management has finalized and made available through its APIs. Delays can occur at the Azure billing layer, during the Turbo360 import cycle, or due to configuration issues in Cost Analyzer. This article explains the common causes of data delays and how to resolve or work around them.

Business value

• Understand whether a data gap is expected platform behavior or an actionable issue
• Avoid incorrect cost decisions based on stale or incomplete data
• Restore current cost visibility as quickly as possible when delays are unexpected

How it works

Cost Analyzer retrieves data from the Azure Cost Management API on a scheduled import cycle. Azure itself finalizes billing data with a lag — typically 24–48 hours for current-day data and up to 72 hours for the previous day's data. Delays in Cost Analyzer may originate from the Azure billing pipeline, the Turbo360 import schedule, or platform-level API throttling.

Troubleshooting

1. Cost data is missing for the current day
   Cause: Azure Cost Management does not provide real-time billing data. Current-day costs typically appear with a 24–48 hour lag as Azure finalizes consumption records.
   Fix: This is expected behavior. Allow 24–48 hours for current-day data to appear. If data for previous days (2+ days ago) is also missing, check the import status for a failed or pending import cycle.

2. Cost data has not updated for more than 48 hours
   Cause: The scheduled import cycle has failed, stalled, or is not running. This may be caused by an expired service principal, a revoked API permission, or a platform-level issue.
   Fix: Navigate to Cost Analyzer settings and check the import status. If the last successful import is more than 48 hours ago, trigger a manual import. If the manual import fails, review the service principal configuration and resolve any authentication errors. See Import issues for detailed steps.

3. Cost group totals appear lower than expected for the current period
   Cause: Azure billing data for the current billing period is still being finalized. Partially finalized data may produce understated totals that will correct themselves as Azure completes its billing pipeline.
   Fix: Compare the cost group total against the Azure portal for the same scope and period. If both sources show the same figure, the data is current and the discrepancy reflects Azure's billing finalization state. If the Azure portal shows a significantly higher figure, re-run the import manually.

4. Forecasting shows a flat line or no projection
   Cause: Cost Analyzer requires a minimum amount of historical cost data to generate a forecast. A new cost group, a recently connected subscription, or a gap in import history may result in insufficient data for projection.
   Fix: Ensure the cost group has at least 7–14 days of complete import history. Resolve any import gaps by triggering manual imports for the missing periods. Forecasting will update automatically on the next successful import after the history threshold is met.

5. Data appears correctly in cost analysis but anomaly detection has not fired despite a visible spike
   Cause: Anomaly detection requires a statistical baseline built from historical data. A newly configured monitor, a recent import gap, or a spend spike that falls within the configured sensitivity threshold may not trigger an alert.
   Fix: Verify the anomaly detection monitor has been active for at least 14 days to establish a reliable baseline. Review the sensitivity configuration and adjust if the spike magnitude should have triggered an alert. Check whether the relevant import cycles during the spike period completed successfully.

Related articles

• Import issues
• Cost analysis
• Automatic anomaly detection
• Common errors
• Monitoring strategies