Common issues

1. 1Confirm you are signed in and the correct workspace is active.
2. 2Reload the page once — a stale view is a common and harmless cause of an apparently broken screen.
3. 3Test a general question with no private data. If that works, the problem is authorisation or data, not the product.
4. 4Test a narrow private-data question against one connected service.
5. 5Read the error text; it usually names the failing stage.

• Blank or empty main area → the view did not finish loading, or a drawer is covering it. Close drawers, scroll to top and reload.
• Answer is empty → check workspace, connected account, and date range. See No data in an answer.
• Answer ignores instructions → the capability may be unavailable; the product states limitations instead of guessing.
• Connection shows connected but fails → reconnect and approve all scopes. See Troubleshoot a connection.
• "Not enough credits" → check which limit was reached. See Credits and limit errors.
• Layout looks clipped or unreadable → reset browser zoom to 100% and reload; zoom below 100% on a narrow window can compress the reading column.

• An answer that cites nothing for a general question — there was nothing to retrieve.
• A capability that reports itself unavailable — a documented limitation, not a failure.
• Different results for the same question later — the underlying data changed.
• A missing button — your plan or role may not include it.

Note the approximate time, the workspace, the exact error text, whether a general question works, and whether a narrow private-data question works. Never include tokens, passwords or provider secrets in a report.