Common Issues

Use this page when something feels wrong in setup or analysis. In most cases, the problem is not “AI quality” in the abstract. It is a mismatch between account scope, source scope, business definition, or evidence strength.

Check:

that you are using the expected email address
that the account you expect to access still exists for your user
that browser security or challenge resources are not blocked

If the browser blocks Cloudflare challenge assets, allow requests to challenges.cloudflare.com.

The wrong account is open

Symptoms:

you cannot find the expected data source
dashboards look missing
billing details do not match expectations

Fix:

confirm the active account first
then re-check the source, cards, or dashboards you expected to see

Many “missing asset” issues are actually account-scope issues.

A data source does not connect

Verify:

credentials are valid
the account has read access
the selected database or schema exists
network allowlists permit the connection path
the source owner agrees the chosen scope is correct

If connection succeeds but analysis still fails, validate with a known simple question before assuming the source is ready.

Answers look wrong

Start by checking:

the question wording
the selected source
the filters and exclusions
the time range
the metric logic

If the same confusion keeps happening, the fix is often semantic modeling rather than more follow-up prompts.

The answer looks polished but not trustworthy

This usually means one of three things:

the business definition is unclear
the source evidence is partial
the question is too broad for the current data context

Do not treat polished language as proof. Re-run with a narrower question or model the business definition first.

A dashboard is stale or confusing