On This Page
Related Documentation
Common issues
The problems people actually hit, with the check that resolves each one.
Common issues
The bell shows nothing
- Confirm you are signed in: GET /api/user/current should return your row, not 401.
- Open the network tab and look for the /api/notifications/live request. If it is not there, reload — the client resubscribes on load.
- Check the workspace switches in /dashboard/team/settings. If memberJoined or wellbeingAlert is off, those events are never recorded for anyone.
- Check your own preferences in /dashboard/settings.
A page is empty but nothing errored
Empty usually means the filter excludes everything, or the workspace has no rows yet. Clear the filters first. Then confirm with a direct read — GET /api/tasks?pageSize=5 — which tells you whether the dataset is empty or the view is filtering it.
A write returns 403
You are signed in as a role that is not allowed to do that. Member management, role changes and workspace settings require admin or super-admin; /admin/cms requires super-admin (or an email listed in ADMIN_EMAILS). Ask an admin, or have your address added to ADMIN_EMAILS to bootstrap the first one.
A write returns 409
The server refused on purpose. The common case is account deletion while tasks are still assigned to you — the message names the count. Reassign or complete them and retry.
CSV import skips rows
"Skip invalid rows on import" is on by default. Turn it off to see which rows fail and why. Rows need at least a title; unknown statuses fall back to todo and unknown priorities to medium.
Charts look flat after a sprint
Velocity and burndown count tasks whose status is done. If work was finished but left in review, the charts will not move. Move the status, then reload.
The AI draft says a provider is unavailable
The generation endpoint reports which model answered. When the configured provider has no key in the environment it says so instead of inventing a draft. Add the key and retry.
Timezones look wrong
Timestamps from the API are UTC (they end in Z). The dashboard renders them in the timezone on your profile. If a due date looks a day off, check the profile timezone rather than the data.
Still stuck
Capture the route, the status code and the response body, then use /contact. Those three things are what makes a report actionable.