Status & Result Codes
Reference for every status, sync type, skip reason, and error code that appears in the admin UI and the Logs tab.
Skip / failure reasons
Reason code attached to a skipped or failed outcome, explaining why a record wasn't written.
|
Value |
Description |
|---|---|
|
|
Skipped because the incoming category isn't in the Category Mapping table and Unmapped Category Handling is set to skip |
|
|
Skipped because the incoming data matches what ExpoPlatform already holds (no-op) |
|
|
The source record was marked deleted — the ExpoPlatform record was removed from the event |
|
|
Skipped by a configured setting (Data Filter, Registration State Filter, etc.) |
|
|
Another record already resolved to the same ExpoPlatform account (typically a shared email) — a warning, not a failure |
|
|
Email First identity matching found a conflict (email match with different External IDs) |
|
|
Failed data validation (required fields missing, format errors) |
|
|
Any other reason not covered by the specific values above |
Sync run statuses
Lifecycle status of a sync run.
|
Value |
Description |
Terminal |
|---|---|---|
|
|
Run is queued and waiting for a worker to start it |
No |
|
|
Fetching data from the source API |
No |
|
|
Iterating through paginated results |
No |
|
|
Dispatching fetched records to workers |
No |
|
|
Run finished successfully |
Yes |
|
|
Run encountered a fatal error |
Yes |
|
|
Run was abandoned after repeated processing failures |
Yes |
Grouping shorthand:
-
In-progress:
fetching,paginating,processing -
Failed:
failed,abandoned -
Terminal:
completed,failed,abandoned
cancelled appears in the vocabulary but is never produced — runs cannot be cancelled once started; they either complete, fail, or are abandoned.
Sync types
Controls how much data is fetched from the source system in a given run.
|
Value |
Description |
|---|---|
|
|
Fetch the complete dataset from the source |
|
|
Fetch only records changed since the last successful sync |
Subscription statuses
Lifecycle status of an integration subscription.
|
Value |
Description |
|---|---|
|
|
Subscription is live and will run scheduled syncs |
|
|
Subscription is temporarily halted; scheduled syncs are skipped |
inactive and deleted exist in the vocabulary but are never produced.
Syncing state
High-level state of a subscription — whether a sync is currently running.
|
Value |
Description |
|---|---|
|
|
No sync currently in progress |
|
|
A sync run is actively in progress |
Trigger source
Records what initiated a sync run.
|
Value |
Description |
|---|---|
|
|
Triggered by a user action in the admin UI |
|
|
Triggered by the every-five-minute scheduler tick |
|
|
Triggered by an inbound webhook from the source system |
Sync error codes
Error codes recorded on a failed sync run.
|
Value |
Description |
|---|---|
|
|
An unclassified error occurred |
|
|
A general sync processing error |
|
|
The subscription referenced by the run no longer exists |