Data is not showing
Most often the data has not been collected yet: CloudYali collects each provider's billing once a day, and nothing is collected at the moment you connect. Wait for the next daily collection, then check the causes below.
| Symptom | Cause | Fix |
|---|---|---|
| Nothing a few hours after connecting | The first collection runs with the provider's next daily run | Wait a day. See Data freshness for the times |
| Months before you connected are missing | Each provider's first collection reads a fixed span: the current month for AWS, two to three months for Google Cloud, six months for most others | Expected |
| A range older than about seven months shows $0.00 | Cost Explorer holds about seven months of AWS, Google Cloud, Azure, Databricks and Fastly cost | Pick a range within the last seven months |
| One provider is missing from a filtered view | Each filter group holds one provider | Add a filter group for the other provider, or clear the filters |
| Every provider stopped at the same time | Your CloudYali subscription has ended, and collection stops | Contact support@cloudyali.io |
| Resources appear but no cost, or the reverse | Cost and resources are collected separately, with different access | Check the provider's section below |
CloudYali does not show a failed collection in the console. If the causes here do not explain it, contact support.
AWS
| Symptom | Cause | Fix |
|---|---|---|
| No cost a day after connecting | AWS has not delivered the first Cost & Usage Report yet, which can take up to 24 hours | Wait for the delivery and the next daily collection |
| No cost at all | The report the stack created was deleted, renamed, or changed to Parquet or to hourly or monthly granularity | Restore the CloudYali-CUR-… report as daily, CSV with GZIP compression |
| A CUR 2.0 or Data Exports report is not read | CloudYali reads only the legacy Cost & Usage Report the stack creates | Keep the stack's report |
| A member account has resources but no cost | Cost comes from the management account's report | Connect the management (payer) account |
| Later AWS corrections to a past month are missing | A month AWS has already invoiced is not read again | Expected |
| Last sync looks wrong | For AWS, the column does not reflect cost collection | Check Cost Explorer for the latest day instead |
Google Cloud
| Symptom | Cause | Fix |
|---|---|---|
| No cost, and Last sync shows — | The console does not show Google Cloud's last sync; the collection can fail without a message. The usual cause is a missing role | Grant BigQuery Job User on the project and BigQuery Data Viewer on the dataset |
| No cost with the standard export | CloudYali reads the detailed (resource-level) export | Point the connection at the table that starts with gcp_billing_export_resource_v1_ |
| Cost starts only at a recent date | The export holds data from the day it was turned on | Expected |
| No Google recommendations in Cost Savings | The recommendations export is not in the billing dataset | Send the recommendations export to the same dataset |
| Corrections older than 15 days are missing | Each collection reads the last 15 days again | Expected |
Azure
| Symptom | Cause | Fix |
|---|---|---|
| No cost a day after connecting | The export has not run, its name differs from the one you entered, or it writes Parquet | Run the export, as CSV, and check its name in Cost Management → Exports |
| A month's file is ignored | The file name has no date range | Keep the export's standard folder layout |
| Only two months appear instead of six | The first collection's six-month read was skipped, because the resource sync or an empty run happened first | Contact support |
| Cost stops after months of working | The client secret expired | Contact support with a new secret |
| No resources or Advisor recommendations | The service principal lacks Reader on the subscription | Assign Reader on each subscription |
Anthropic, OpenAI and Cursor
| Symptom | Cause | Fix |
|---|---|---|
| Anthropic or OpenAI: nothing until the next day | The first collection runs at about 14:30 UTC | Wait |
| Anthropic: Claude Code usage is missing | The Claude Code usage report is not available for your organization | Expected |
| OpenAI: Last sync stops moving | After five failed collections in a row, often a revoked key, CloudYali stops collecting | Contact support with a new admin key |
| Cursor: the team stops updating | After five failed collections in a row, often a revoked or non-admin key, CloudYali stops collecting | Select Replace key with a new team Admin API key |
Fastly and Databricks
| Symptom | Cause | Fix |
|---|---|---|
| Fastly shows $0.00 most days and a jump on the 1st | Fastly bills monthly, so its cost is dated the 1st | Use Monthly granularity |
| A new Databricks account shows nothing | Databricks system tables fill a day or two after the account starts | Wait |
| A second Databricks workspace has no history | The six-month first read applies to your first workspace only | Contact support |
Still stuck
Email support@cloudyali.io with the provider, the account or project ID, when you connected it, and what is missing. Do not send keys, secrets or key files.
Related
Was this page helpful?