Documentation Troubleshooting ▾
Troubleshooting
Check channel access and import coverage first. /recall status shows what RecallHQ can currently search.
The installation link shows an error
Check that you selected the intended workspace. Slack may require admin approval, and installation in another workspace requires the app owner to enable distribution. If the hosted pilot is unavailable, try again later or ask the app owner to check the service.
My channel is missing
Invite @RecallHQ to that channel and confirm you are a member. Then run /recall status. The bot does not discover or ingest every workspace channel automatically.
Old messages aren’t searchable yet
Use /recall status to inspect coverage and import errors. Slack can limit history and replies to one request per minute per method and workspace, with small pages. Imports can therefore take substantial time.
An admin or owner can retry a failed import with /recall sync #channel. Messages unavailable through Slack’s APIs cannot be imported.
A new message is missing
Live capture and embedding run asynchronously. Check the backlog in /recall status and wait for indexing. Ensure the message is channel text, rather than a file attachment or DM.
The answer says there is not enough evidence
Try a more specific question or use /recall search to inspect the original messages. Check your channel filter and history coverage. RecallHQ may suppress an answer when its evidence was edited, deleted, or became inaccessible, or when the model cites a message it was not given.
The recap is partial
Catch-up ranges are capped at 32 days. Large message counts, unusually long messages, context limits, or unfinished history imports trigger a coverage notice. Narrow the dates or channel to make the recap more complete.
The playground has reached its limit
Anonymous demo limits are three commands per minute and 20 per day per visitor IP, with a shared daily cap. Wait before retrying. You can still browse the synthetic archive.