FAQ and troubleshooting

Why does month-to-date cost stop two days ago? #

Billing data is not final immediately. Flux excludes unfinalized days from totals, forecasts, and anomaly baselines rather than showing a figure that will change.

Working as intended. See Data sources and freshness.

Why is my anomaly detection “warming up”? #

It needs enough matching-weekday history to build a robust baseline. Until then, Flux reports the warming-up state rather than producing findings from thin evidence.

Typically several weeks. It resolves itself.

Why do actual and amortized cost differ so much? #

A commitment purchase appears in full in actual cost for the month it was bought, while amortized spreads it across the term it covers.

Use amortized for trends, actual for invoice reconciliation.

A resource shows no utilization — is it idle? #

No, and Flux will not say it is. Not covered means no telemetry was available, which is a coverage gap, not evidence of idleness.

Check the resource’s telemetry sources under Opportunities.

Why is my allocation coverage low? #

Spend on resources carrying none of the configured cost-centre tags is unallocated.

Run the tag hygiene report and work the costliest untagged resources list top-down — tagging ten expensive resources usually moves coverage more than tagging a hundred cheap ones.

Two people see different numbers #

Compare the snapshot version each is on, shown in the header. Serving instances adopt a new published version within a refresh interval, so a brief difference during a publication is expected and resolves in under a minute.

If versions match and numbers differ, check whether the filters or cost type differ — that is the usual cause.

The commitments section is missing #

It requires charge-level billing exports in FOCUS format. Without them, the section is hidden rather than shown with hollow numbers. See Connecting your cloud.

Flux Intelligence says it cannot answer something #

Usually one of two things.

No deterministic engine exists for what was asked — commitment purchase planning is the common case. The assistant is required to say so rather than improvise a number.

The question exceeded its tool budget. Narrow the scope — a subscription, a service, a shorter window — and ask again.

Sync appears stuck #

Check the pipeline status endpoint, which reports claims and their ages. A claim expires after its lease and is recovered automatically by the next worker; work is not stranded by a crash.

Persistent throttling on very large estates is normal — Flux paces requests deliberately to stay inside API quotas, and reports throttled scopes rather than hiding them.

Can Flux change anything in my cloud? #

No. It holds read permissions only and has no code path that mutates cloud resources. See Security and data handling.

Can I export everything? #

Yes. Inventory, cost, opportunities, anomalies, and reports export to CSV or Excel with filters applied. Excel carries provenance metadata. Individual findings export as deterministic evidence packs suitable for a change request.