Troubleshooting & support

Forgotten or rejected password. Use the “Forgot password” link on thesign-in page to receive a reset email. If it doesn't arrive within a few minutes, check spam and confirm you are using the same address you signed up with.

Signed up with Google or Microsoft. If you created your account with social sign-in, there may be no password to reset — use the same “Continue with Google” or “Continue with Microsoft” button you used the first time. You can connect another sign-in method from Settings after you are signed in.

The page loops back to sign-in. This is almost always a stale session cookie. Sign out fully, clear cookies for the app domain, and try again in a normal (not private) window.

First, reload the page — the editor collaborates in real time, and a dropped connection can leave a stale view. If it is still blank:

1. Confirm you are online and can reach the rest of the app.
2. Check that you still have access — a report shared with you can be un-shared by its owner.
3. Try another modern browser to rule out an extension interfering with the canvas.

If the report opens but a chart or table is empty, the issue is usually the data behind it rather than the report itself — see the next section.

When a report stops updating, the connection to your source is the first place to look.

Credentials changed or expired. Rotated a database password, or a token that has lapsed, will make a refresh fail. Re-enter the connection details on the source, then run the refresh again.

Schema drift. If a column was renamed, removed, or retyped at the source, bindings that pointed at it can break. Rahoto detects schema changes and surfaces them so you can remap the affected fields rather than silently dropping them. Re-open the source and follow the mapping prompts.

The source is unreachable. A firewall change, a paused warehouse, or an IP-allowlist that no longer includes Rahoto will all read as a connection error. Confirm the source is up and reachable, then retry. Full setup steps live inConnect your data.

Exports and scheduled deliveries run as background jobs, so a large report can sit in a “pending” or “running” state for a short while before it completes — that is expected, not a failure. If a job stays pending well beyond a typical export:

1. Give it a moment and refresh the job list — most complete on their own.
2. Confirm the report's data has refreshed successfully; a delivery waits on its data.
3. For a scheduled run, check the delivery target's settings (address, channel, or access policy) are still valid.

Details on schedules, variants, and delivery targets are inPublish & schedule.

Rahoto renders most reports in any current browser. Very large datasets (charts plotting many thousands of points) draw on the GPU, which needs a WebGL2-capable browser. If a dense chart looks slow or falls back to a simpler view, update to the latest version of Chrome, Edge, Firefox, or Safari and make sure hardware acceleration is enabled. Smaller charts and everything else are unaffected.

Every scheduled report keeps a record of its runs — when each one fired and whether it delivered. It is the fastest way to confirm a report went out, or to see which run failed and why. Open the report's publishing view to find its schedule and run history;Publish & schedule walks through it in full.