You are here:
Replication Error States
Failed B2C Commerce process-level replication events (sf.cc.replication.failed)
include an errorState field with a machine-readable code that identifies the
failure. Use this page to look up what an error state means.
| Value | Description |
|---|---|
ERROR_INITIALIZATION |
Replication process could not be initialized |
ERROR_STAGING_PROCESS_CREATION |
Could not create staging process |
ErrorInternalLive |
Internal error in target system |
ErrorInternalEdit |
Internal error in source system |
ErrorNonStagedParentSites |
Selected content belongs to sites not yet replicated |
ErrorConnectLiveSystem |
Could not connect to target system |
ErrorCreatingLiveStagingProcess |
Failed to initialize process in target system |
ErrorExecutingEditingStagingPipeline |
Internal error in source system pipeline |
ErrorLiveStagingProcessKilled |
Process aborted in target system |
ErrorEditingStagingProcessKilled |
Process aborted in source system |
ErrorStagingProcessCancelled |
Process was cancelled |
NoStagingProcessCreated |
Process could not be initialized |
ErrorStagingProcessModeNotSupported |
Process mode not supported |
ErrorTableLocked |
Locked database table |
ErrorInitializingStagingProcessors |
Could not initialize processors |
ErrorCallingLivePipeline |
Connection to target system failed |
ErrorSynonymState |
Critical invalid internal state on target |
ErrorAcquiringEditingLocks |
Could not acquire locks in source system |
ErrorAcquiringLiveLocks |
Could not acquire locks in target system |
ErrorPreparation |
Preparation failed in source system |
ErrorRefreshCache |
Cache refresh failed in target system |
ErrorReplication |
Data transfer to target system failed |
ErrorPublication |
Publishing of transferred data failed |
Notes
- These values are machine-readable codes, not localized text. Use them as-is when building automation logic in your connector.
- Granular replication events use a separate
failureStatusfield instead oferrorState. See Granular Replication Events.

