FinOps Data Missing or Stale Playbook

Who this is for

Users whose FinOps cost dashboard shows no data, stale data, or missing costs for specific services.


Understanding FinOps Data Freshness

CloudAIPilot pulls billing data from each cloud provider on a scheduled basis. Each provider has its own data refresh schedule and latency:

ProviderTypical data delay
AWSUp to 24 hours (Cost Explorer is updated daily)
GCPUp to 48 hours (Billing export to BigQuery)
AzureUp to 24 hours (Cost Management API)
DigitalOceanNear real-time (invoice API)

Today's costs are never complete. Partial-day data is normal — expect the current day's costs to be fully accurate the following day.


Step 1 — Check the Last Sync Timestamp

  1. Go to FinOps in the sidebar.
  2. Look for the Last updated timestamp on the cost dashboard or in the data source details.
  3. If the last sync was more than 48 hours ago, there may be a data collection issue.

Step 2 — Check Cloud Account Status

FinOps data collection requires the cloud account to be active with billing permissions.

  1. Go to Cloud Accounts.
  2. Verify the affected account shows active status.
  3. If it shows error: fix the credentials — see KB-12-04: Cloud Permission Denied Playbook.

Step 3 — Check Billing Permissions (Per Provider)

FinOps requires additional billing-specific permissions beyond basic server management:

AWS:

  • IAM role must have ce:GetCostAndUsage (Cost Explorer) permission.
  • Cost Explorer must be enabled in the AWS account (it is not enabled by default in new accounts).

GCP:

Azure:

  • Service principal must have Cost Management Reader role.
  • Subscription must have billing export configured.

DigitalOcean:

  • API token requires read permission — standard token is sufficient.

Step 4 — Trigger a Manual Data Refresh

If your billing permissions look correct but data is stale:

  1. Go to FinOps → Settings (or the cloud account detail).
  2. Click Sync Now to trigger an immediate data pull.

If the sync fails, check the error message in the Activity Center.


Common Scenarios

SymptomCauseFix
No data at allCloud account not connected or credentials invalidConnect cloud account and add billing permissions
Data present but stops at a dateCredential expired on that dateRotate credentials — see KB-01-06
Some services missing from cost breakdownService not supported in the billing API filterThis is a provider-side limitation. Check provider coverage.
Current month costs look lowData delay (normal)Today's costs are incomplete. Check tomorrow.
Forecast seems wrongInsufficient historical data (<30 days)Forecast models need at least 30 days of data to be accurate

Related Articles