Troubleshooting
Find why a Slack message, a Cal.com booking or a mailbox resolves to the wrong account or to none.
Reviewed 2026-10-28Markdown
Start from the account row and its binding. Check what the base holds before changing a workflow or creating a replacement row.
| Symptom | Check | Recovery and confirmation |
|---|---|---|
| Slack message fails with BOT_NOT_CONFIGURED | A Tool Account with Kind = bot linked to the workspace that has that External Identifier | Fix the bot’s Workspace link or Kind; the next five-minute refresh picks it up |
| AMBIGUOUS_BOT or CACHE_DUPLICATE | Two bot accounts on one workspace | Keep one bot per workspace; see Workspace cache |
| Digest DM fails with user_not_found | Recipient’s open binding, the human account’s workspace, duplicate names in Person (mirror) | Close the wrong binding or fix the account’s Workspace; the resolver ignores Valid From |
| Cal.com booking arrives without a seller | Account External Identifier (username) and Login Alias here; Lead Source rule in CRM | Fix the account here, wait for the CRM copy, then the rule. See Onboard a seller |
| Field missing in the CRM copy | Whether the field is in ops:ToolAccount Sync | Bound Person and Bound Membership are not in that view today |
Workspace URL shows missing app url |
Tool → App url | Fill App url on the tool |
| Account Name ends with an id | Workspace link and the workspace’s Company | Link the workspace or its Company |
| Bound Person shows two people | Open bindings for the account | Close one with Valid Through |
| Person not in the picker | Core People and the sync | Create or correct the person in Core and wait for the mirror |
| A token appears outside the base | Where it was seen | Rotate it in the tool and report it; see Secrets |
Escalation evidence
Give the maintainer the table, view, account Name or External Identifier, the workflow name and error code, and the approximate time with timezone. Do not include tokens, full message payloads or personal e-mail addresses.