09.1 The Problems page
Anything that fails in the background, such as a table copy, a cube build or a scheduled job, lands on Problems. You don't have to look for it. When something's open, the menu item shows a red count.
Two kinds of problem
! Failed: something ran and failed.
- Shows the message, what it happened to, and how often (3 times, first … / last …). The same failure repeating is one row with a count.
- Detail shows the full technical detail and, for table copies, the log.
- Mark as done when it’s dealt with.
⏸ Stopped: something stopped without finishing, e.g. the server restarted mid-way.
- Log shows what it was doing.
- Clear it frees things up. A stuck cube build blocks later builds of that cube until it’s cleared.
- If it says not confirmed, it may still be running. Wait a little before clearing.
What to do
- Open Detail or Log and read the cause.
- Fix it at the source: a connection’s password changed, a table was renamed, the database was down…
- Run it again: Load now (table), Build now (cube) or Run now (job).
- Mark as done (or Clear it).
Tick Show the ones already dealt with to see past problems.
Who sees this page: by default, company admins and super admins.
Problems on a dashboard
A dashboard has its own Problems badge (red: widgets can’t run; amber: worth checking). Click it to see what’s wrong and which widgets are affected, with a fix button such as Open the dataset → or Add a filter tagged … →. See 09.2 Common questions.
Next: 09.2 Common questions
Last updated 12 October 2026