Troubleshooting
Common issues and what to do. If your problem is not listed, contact your workspace admin.
"Please sign in"
Your session expired or you are not authenticated. Refresh the page; you may be redirected to the login screen. If you stay on the same page, your token is missing — sign in via the workspace login.
"Please switch to a workspace"
You are signed in but no workspace context is set. Click the workspace switcher in the top-left and pick a workspace.
"Access denied" or actions are greyed out
You do not have the permission required for that action. Each conversation action maps to an RBAC permission:
| Action | Permission |
|---|---|
| Open the Conversations page | conversation:read |
| Create a conversation | conversation:create |
| Send a message | message:create |
| Edit your own message | message:update |
| Edit anyone's message | message:moderate |
| Delete your own message | message:delete |
| Delete anyone's message | message:moderate |
| Add / remove members | participant:add / participant:remove |
| Pin / unpin a message | message:pin |
| Hide a message | message:moderate |
| Archive / restore a conversation | conversation:archive |
Ask your workspace owner to grant the permission via the role assigned to you.
Messages not appearing in real-time
Conversations uses GraphQL subscriptions over WebSockets. If realtime is broken:
- Refresh the page — confirms whether it is a transient WS issue.
- Check your network tab for
/workspaces/graphqloverwss://. If absent, the WebSocket connection failed; check for browser extensions or corporate proxies blocking WS. - If the symbol next to the conversation title shows "Reconnecting", wait a few seconds — the gateway auto-retries.
If real-time stays broken even after refresh, the gateway may be having trouble. Contact your workspace admin.
Notifications not arriving
Run through these in order:
- Confirm the conversation's notification level (header → Bell icon) is not set to NONE.
- Confirm you are not within a quiet hours / DND window.
- Confirm the channel (in-app, email, push) is enabled in your global notification preferences.
- For push specifically, confirm the browser/device has push enabled and notification permission granted.
If everything looks right but no notifications arrive, ask an admin to check the notification service logs.
Search returns nothing for a phrase you remember
- Search uses English text-search rules — exact stemming differences (e.g., "running" vs "run") are normalised, but proper nouns and code-like strings may be tokenised oddly. Wrap them in quotes.
- Very recent messages (last few seconds) may not yet be indexed; the indexer runs slightly behind realtime.
- If the message was hard-deleted (rare; Owner-only), it is not searchable.
Cannot leave a conversation
- DMs cannot be left — only archived.
- Channels and groups: if you are the only Owner, promote someone else first, then leave.
Cannot remove the last Owner
The system requires at least one Owner per conversation. Promote another member to Owner first.
A file attachment shows as "Failed"
The Files service rejected the upload. Common causes:
- File size over the workspace's per-file limit.
- File type blocked by workspace policy.
- Storage quota for the workspace exhausted.
Hover the failed attachment for the specific error code, and forward it to support if the cause is not obvious.
I see an error code I don't recognise
Error codes in conversations follow this pattern:
UNAUTHENTICATED/FORBIDDEN— auth/RBAC.NOT_FOUND— conversation or message no longer exists, or you lost access.BAD_USER_INPUT— the form has invalid data.CONFLICT— concurrent edit; retry usually fixes it.RATE_LIMIT— slow down; you are sending too fast.INTERNAL_SERVER_ERROR— an unexpected backend error. Note the request ID shown in the toast and forward it to support.
Still stuck?
Use the workspace help channel or file a bug from the workspace help menu. Include:
- The URL you were on.
- The exact error message and request ID (if shown).
- What you were doing.
Engineering will trace your request via the request ID in the activity service and the SRE traces.