Why changes don't bounce back
Why a change HubConnector writes to one platform does not sync straight back to the platform it came from, and where to see it in the audit trail.
When HubConnector writes a change to a platform, that platform reports the write back, either through a webhook or the next poll, the same way it would report any other change. Without a way to recognize its own writes, HubConnector would sync that change straight back to the platform it came from, and back again, in a loop.
What this means for you
- A change HubConnector writes to one platform is not synced back to the platform it came from.
- Routine metadata that a platform updates on every save, such as its own last-modified date, does not count as a change on its own.
- When someone genuinely edits the record afterwards, that edit is a real change and syncs as normal.
Where to see it
Every skipped echo is recorded as an Echo Suppressed event in the audit trail. See Read the audit trail.
Right after two records are first linked, an edit made within moments of the link may be treated as an echo. If a change you expected is missing, search the audit trail for an Echo Suppressed event on that record, then make the edit again to sync it.