Troubleshooting
I cannot create a project
Check workspace selection, required fields, permissions, and project limits.
I cannot create a tracker row
Check that the project name is filled, the workspace is selected, and your role can edit tracker data.
Search shows unrelated draft rows
Draft rows should be filtered together with saved rows. If unrelated draft rows remain visible after search, rebuild the frontend with the latest Collab Tracker update.
CSV export includes too much data
CSV export should respect the current filters, search, selected sheet, and visible rows. Check that you are using the latest Collab Tracker file.
I cannot copy a tracker cell
On desktop, right-click the cell. On mobile, long-press the cell. If nothing copies, check browser clipboard permissions.
A tracker link will not open
Hover the link cell on desktop and use the open-link action. On mobile, tap the link action. Confirm the saved value is a valid URL.
Alphabot says rate limit exceeded
Stop manual syncs temporarily, wait for the rate limit to reset, keep statuses limited to Active and Finalized, and confirm backup sync is not too frequent.
Discord commands are missing
Restart or redeploy the backend bot so slash commands are registered again for the connected server.
/winners-sheet cannot find my project
Use the project autocomplete and search by the grouped project name. The command should target main grouped project rows rather than individual raffle rows.
A Discord command says I do not have access
Make sure your Discord account is connected to your CollabOS profile and that you are an active member of the workspace with a permitted role.
Discord login redirect fails
Confirm the exact Discord OAuth redirect URL exists in Discord Developer Portal and the backend environment variables match it exactly.
A Discord role action fails
Check the bot permissions and role hierarchy. The CollabOS bot role must be above the roles it needs to manage.
A bulk role command assigns to the wrong group
Check the target option before running /bulk-assign or /bulk-remove. For channel-based actions, confirm whether the command is using current voice/stage members or recent text-channel participants. Use exclude_bots when bots should not receive roles.
Role history recovery returns limited data
Discord audit logs are limited. /recover-role-history can only recover recent role assignment events that still exist in the audit log and that the bot has permission to read.
Sync command does not update members
Check that the bot is still in the server, has member intent enabled, can read the server, and that the Discord server is connected to the correct CollabOS workspace.