Troubleshooting
Common statuses and errors, in plain English.
Short explanations for the messages, symptoms, and failure states people are likely to hit first.
Access issues
Message or symptom
What it usually means
Best next step
Sign-in succeeded, but the dashboard session could not be verified
Account sign-in worked, but protected dashboard access did not resolve cleanly.
Retry the session exchange and check access verification before serving dashboard data.
You can sign in, but you cannot see the queue
The account may be valid, but the role or tenant context is not.
Check role mapping and tenant scope before assuming the queue is empty.
The page loops back to login
Session verification expired or failed before the dashboard request finished.
Check the short-lived session path and its failure behavior.
Connector issues
Message or symptom
What it usually means
Best next step
A field is missing from recommendations
The connector may not expose the field, or the mapping is incomplete.
Check connector scope, plan limits, and field verification.
A connector looks connected but the queue is thin
The connection succeeded, but the useful signal is still weak.
Check freshness, field coverage, and data quality before trusting the queue.
The queue suddenly looks stale
The last successful refresh may be older than the team expects.
Read the freshness state and confirm the source data changed.
Queue issues
The most common queue problems are not glamorous. The list is too long, too thin, too vague, or too confident with bad data. A useful error surface should help the team sort those cases quickly instead of forcing everyone to reverse-engineer what the product was thinking.