Troubleshooting
Find the cause of missing records, stalled follow-up or incomplete bookings.
Reviewed 2026-11-06Markdown
Start with the record and its current state. Avoid replaying or creating a replacement before checking what was already persisted.
| Symptom | Check | Recovery and confirmation |
|---|---|---|
| Record vanished after editing | Intake Step and current filter; closed states leave queues | Find it in the general/By Company view and verify its values |
| Assigned lead missing from a filtered view | Deal → By Creator groups by Created By, not by Accountable (Person)* | Use Leads or the company view for the seller; the automation that created a Deal is not the seller |
| Next action of a sale not visible | Nothing copies Interaction.Next Action° to another table | Add or update the task in Tasks; check Overdue and Upcoming |
| Deal Name says No client | Company° and People° empty, possibly delayed mirror | Resolve Core identity and link the person or company on the Deal |
| Booking arrived without a seller | Lead Source active flag, Tool, account identifiers and target pair | Fix routing and repair existing ownership; replay can stop as duplicate |
| New Person never appeared | Core existence, Proposed status, sync mapping and ten-iteration wait | Repair sync or link the source identity after it arrives; do not duplicate it |
| Signature rejected | Shared secret, x-cal-signature-256 and JSON serialization | Reconcile sender/verification configuration without disabling verification |
| Same lead counted twice in a campaign | Deals (Campaign) on the Campaign mirror lists two open Deals for the same client | Keep one Deal, move its Interactions and Tasks to it, then close the duplicate as Abandoned |
| Campaign unavailable for enrollment | CRM Campaign Check, Active and deletedAt | Correct source facts in Core and wait for sync; inspect Grid view for drafts |
| Interaction shows the wrong campaign | Interaction.Campaign is a lookup through Deal° | Fix Campaign° on the Deal, or link the right Deal° on the Interaction |
| Health looks complete but warning remains | Presence score versus consistency formula | Resolve the named warning; a score is not validation of truth |
| UUID absent on an old record | Creation automation run and audit history | Recover original UUID; recordCreated does not rerun after clearing a field |
Escalation evidence
Give the maintainer the table, record locator, approximate time/timezone, expected transition and failing node name or error code. Keep credentials and full contact payloads out of shared diagnostics. See Cal.com recovery for replay limits and known gaps for unresolved configuration differences.