Help Center
How can we help?
Step-by-step answers for PVology, written for what you are trying to do.
Sync, failed records & conflicts
- Automatic retries and writes PVology could not confirmWhen the other system cannot be reached, times out, limits requests or answers a server error, PVology retries automatically after about 1 minute, 5 minutes, 30 minutes and 2 hours (with a small random spread), at most 4 times. Validation and permission errors are not retried. When an answer to a write is lost, PVology checks first and never repeats the write blindly.
- How to resolve a sync conflictA conflict means the same field changed in PVology and in the other system since the last sync. Nothing was overwritten: open Connect → Sync → Conflicts, compare both values and choose Keep PVology's value, Use the other system's value, or decide another value, then Resolve this conflict.
- How to retry, skip or resolve failed recordsConnect → Sync → Failed records lists every record that did not go in, with the reason. Fix the cause, then choose Retry selected (or Retry this record); choose Skip it with a reason, or Mark resolved when it was fixed by hand. Records are never dropped silently.
- How to set up a two-way sync safelyTwo-way is never the default. Set the connection's direction to Both ways (controlled) and its source of truth to Controlled two-way, then give every mapped field one owner, PVology or the other system. PVology sends back only the fields it owns and never re-sends a change that came from the same connection.
- How to start a manual sync or choose a scheduleOpen the connection and, under Sync, choose Run sync for a kind of record (it needs an active mapping). To sync regularly, choose a schedule (manual, hourly, daily or weekly) and Save schedule.
- Troubleshoot a schema change (the other system's fields changed)When a mapped field is removed, renamed or changes type in the other system, the sync stops before writing and the connection shows Schema changed: syncs are paused. Read the fields again on the mapping, fix it, test it, dry-run and activate the new version.
- Understand sync resultsA job shows how many records were read, created, updated, unchanged, skipped, in conflict and failed, and lists every record with its outcome and reason. Its status is worked out from the counts: Success, Success with warnings, Partial, Requires review, Retrying, Failed. A sync is never shown as completed when records failed.
- Why a field says "Managed by" another systemWhen a connection is the source of truth for some fields, those fields show Managed by <connection name> on the record and cannot be edited in PVology (also not through the API or an incoming webhook). Change the value in the other system; the next sync brings it in.
- Why did this integration (or sync) fail?Open the job (Connect → Sync) or the connection and read Why did this happen?: the reason code and a plain explanation, for example the credential was rejected, the other system could not be reached or limited requests (retried automatically), its fields changed, or records were refused by validation. Each reason gives the next step.
Still need help?
PVology Support creates a request for you at once, answers ordinary questions straight away and brings in a specialist when needed.
Contact PVology →