CRM or helpdesk sync is failing

A failing CRM or helpdesk sync almost always traces to one of four causes: expired credentials, a broken field map, a destination rate limit, or a record-ownership conflict between the two systems. Check them in that order — credentials first, since an expired token stops the entire sync rather than a subset of records.

Diagnostic sequence

1. Credentials. Confirm the OAuth connection under Settings → Integrations still shows Connected rather than Needs Reauthorisation. Tokens expire on the destination system's schedule, and a connected user losing admin permissions in the CRM can also silently invalidate the token.
2. Field mapping. Open the integration's field map and look for any destination field marked required with no source field assigned. A single unmapped required field rejects the whole record, which is why one bad mapping can look like "nothing is syncing" even though most fields are fine.
3. Rate limits. Check the sync log for throttling responses from the destination API. A rate-limited sync usually resumes on its own after a cooldown period, so what looks like a stalled or failed sync may simply be delayed — compare log timestamps to when records actually appear in the destination.
4. Ownership conflicts. If specific fields keep reverting to old values, two systems are both configured to write that field, and each sync cycle undoes the other's update. This is the least visible cause because each individual sync "succeeds."

Cause and fix

Fixing ownership properly

Bidirectional sync without a declared source of truth per field is the single most common cause of "the data keeps changing back." The fix is not technical but organisational: for every synced field, decide which system owns it — for example, the CRM owns lifecycle stage, while Arino One owns last-contacted timestamp — and configure the integration so the non-owning system only reads that field rather than writing it. This eliminates the update loop entirely rather than just slowing it down.

Escalation path by connection state

Whether the instance has an active $50/month Arino Core connection determines whether Arino support can look inside the sync configuration.

When escalating, include a specific failing record ID, the field or fields affected, and the timestamp of the failed sync attempt — this is the minimum information any support channel, Arino or otherwise, needs to trace a specific sync failure rather than a general pattern.

Steps at a glance

1. Re-check credentialsExpired or revoked tokens are the most common cause of a sync stopping entirely. Reauthorise the connection from Settings → Integrations.
2. Review the field mapA required field on the destination system with no mapped source field rejects the entire record, not just that field.
3. Check rate limitsDestination API limits cause partial syncs that quietly resume later rather than failing loudly, which can look like missing records.
4. Resolve ownership conflictsDecide which system is authoritative per field so two-way updates stop overwriting each other in a loop.
5. Escalate with a sample record and timestampIf credentials, mapping, rate limits, and ownership are all confirmed clean, escalate with a specific record ID and the time of the failed sync attempt.

Frequently asked