Troubleshooting

I cannot create a project

Check workspace selection, required fields, permissions, and project limits.

I cannot create a whitelist campaign

Check the selected workspace type and role. NFT Project, Web3 Project, and Agency workspaces can create campaigns. A Viewer should not be able to create or manage campaigns.

My community cannot apply to a whitelist campaign

Check that the application is using an eligible Community, Alpha Group, or Agency workspace and that the campaign is still available for applications.

A campaign does not appear in Whitelist Campaigns

Confirm the campaign is published/open for public discovery and that its application deadline has not passed.

My GTD sheet is finalized but FCFS is still editable

That is expected. GTD and FCFS use independent winner submission states. Finalizing one does not automatically finalize the other.

I cannot edit a finalized GTD or FCFS sheet

Finalized winner sheets are locked. The relevant sheet must be reopened before it can be edited again.

The GTD or FCFS winner count does not match the approved allocation

Review the approved GTD or FCFS allocation and the winner rows in that same allocation type. Do not mix GTD rows into the FCFS sheet or FCFS rows into the GTD sheet.

A winner row is flagged as a duplicate

Check the campaign duplicate policy for wallet, Discord ID, and X account. The campaign can allow, flag, block, or keep the first matching win depending on project settings.

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. For whitelist winner exports, also confirm whether you are viewing All, GTD, or FCFS.

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 the intended sync states, 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 add cannot find my project

Use the project autocomplete and search by the grouped project name. The command should target the main grouped project row rather than an individual raffle row.

/pullsheet cannot find a sheet

Confirm a winners sheet link has already been saved for the matching project or group.

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 role expiry did not behave as expected

Check the role expiry policy and whether the individual assignment has an explicit expiry. An explicit per-assignment expiry takes precedence over the normal policy.

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 or stage members or the supported text-channel participant behavior. 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.