Sync details

This page explains how a connection keeps records in step: its groups and owners, how records are matched, and what happens to records that could not be synced or were deleted at the source.

Connector groupsCopy Anchor Link

Each organisation classifies a connector as Business, Non-business or Blocked. A connector with no classification is blocked. A flow cannot mix business and non-business connectors. Directory connectors allow reading and listing only. The Activepieces platform connector and the PostgreSQL connector stay blocked.

OwnersCopy Anchor Link

Each connection has an owner and a different backup owner. Both are members of the organisation.

• If the owner leaves and the backup is still a member, the backup becomes the owner.
• If neither remains, the connection is suspended until someone assigns a new owner.
• A connection whose credential has been withdrawn cannot be used.

Record identityCopy Anchor Link

A sync remembers which external record belongs to which Akollo record, including the source system and the record version. A later sync updates that same record. An older version never replaces a newer one. A support session can look at a sync but cannot change it.

Records that could not be syncedCopy Anchor Link

A record that cannot be synced is set aside, and the rest of the sync goes on. Records that failed for the same reason are grouped together, with the number of failures and when the problem was first and last seen.

The saved copy of a record is encrypted. Only field names, value types and lengths are shown, and the copy is deleted after 30 days.

An administrator can retry one record or many at once, for example after fixing a mapping. A retry reads the record again from the source and uses the mapping in force at that moment. The saved copy is used only while the source cannot be reached. It is never used when it is older than the version already synced; the record then stays in the list. A record that later syncs successfully leaves the list on its own.

An administrator can also skip a record with a reason, resolve a conflict, or download the list as a CSV file that contains no record content.

Sync streamsCopy Anchor Link

Each sync stream of a connection is listed on the connection's Syncs tab with its state, last run and published mapping version. The stream page shows:

• the recent runs: kind, records read, written and set aside, duration and result;
• where the stream stopped reading;
• the mapping version.

A stream that never ran says so. A partially synced stream shows how many records wait in Issues, with a link there. A permitted user queues a new run with Run now; while one is waiting, a second one is not added. A stream can be paused with a reason and resumed. A paused stream shows the date it was paused and cannot be run.

Field mappingCopy Anchor Link

The mapping page shows, for each Akollo field:

• its field in the external system;
• the source of truth: Akollo, External system or Both ways;
• the transform;
• what happens on a conflict and on a delete.

A draft that opens a protected field to the external system waits for a different admin than the first publisher to approve it. Meanwhile the page says who is waiting for approval. On a phone the mapping is read-only; editing needs a larger screen.

Issues screenCopy Anchor Link

The Issues tab groups the records a sync set aside by cause. Each group shows the cause, how many records and how many times, first and last seen, and the streams involved. Opening a group lists its records.

A record's fields show only their names, types and, for unprotected fields, their length. Values are never shown. For a record whose saved copy expired, the screen says a retry reads it again from the source.

On a larger screen you can select records and retry them together, or skip them with a reason. A conflicting field is resolved with the Akollo value and the external value side by side: Take Akollo, Take external, or Enter value. A protected field's values are not shown here either. The list can be downloaded as a CSV file that carries no record content. With no open issue, the screen says so, with the last check time.

Records deleted at the sourceCopy Anchor Link

Once a week the connection compares the full list of records at the source with the records it has linked. A record is treated as deleted only after two complete comparisons in a row have not found it. An incomplete or interrupted comparison never deletes anything.

What happens to the Akollo record (archive, detach, ignore or disable) is set on the sync. If the owning part of Akollo refuses the deletion, the record appears among the records that could not be synced.

FAQCopy Anchor Link

Related pagesCopy Anchor Link

• Connected systems
• API and keys