Troubleshooting

A consumer shows an old value

Impact: the consumer acts on an outdated fact. Check the value in Core first. If Core is right, the mirror has not refreshed or does not include the field: open the sync settings in the consuming base and check the source view, the included fields and the last refresh. Correct nothing in the mirror. If Core is wrong, correct Core and wait for the next sync.

The same person or company appears twice

Impact: links split between two records and reports count twice. Search People by Email* or Organizations by Website°. Typical causes: a row created in the CRM and another in Core before the sync arrived, or a booking with a different e-mail. Keep the older record, move links, mark the other Superseded and note the survivor in Notes. Do not delete a row that a mirror may still reference.

A new person has no Status

Impact: the row does not appear as Proposed and can be missed. Rows created from the CRM or by hand have no default Status. Set Proposed or Active after checking for duplicates. A Work Item proposes an automation to set Proposed.

A booking created no CRM person

Impact: the CRM Deal and Interaction may lack People°. The booking workflow created the Core Person and waited up to ten minutes for the CRM mirror. Confirm the Person exists in Core with the tag cal-lead-n8n, then wait for or trigger the CRM sync and link the person in People° of the Deal and the Interaction. See Cal.com booking for recovery.

Campaign Check says “Waiting for campaign identity”

Impact: the campaign cannot be activated cleanly and the CRM mirror has no stable key. The coreId automation runs only on creation. Confirm it is deployed in Automations. If the row was created before deployment, or coreId was cleared, restore the original UUID if one existed; otherwise ask the owner before writing a new one.

Health check lists missing fields

Impact: the record is incomplete, not invalid. Fill the fields it names. For Address, a ZIP code with a leading zero cannot be stored correctly yet; record the issue rather than altering the code.

A link shows a number instead of a name

Cities, States and Countries use an auto-number ID as primary field, so a link to them shows a number. Read the lookups next to the link, such as City: Name [CY] in Address. This is a schema limitation, not an error.