---
schema_version: "1"
id: 020c97ff820041d66e021bd2ea9bbb4f9aa4c2dbff21a9fbe703cfaaed90be09
title: Replication Error States
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_event_replication_error_states.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_event_replication_error_states.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ac8c6cf2796a1ab377f4fa8e1bb6c3fa180718c920f60aa3ed64af1c38ab2314
description: 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.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# 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 `failureStatus` field instead of `errorState`. See [Granular Replication Events](https://help.salesforce.com/s/articleView?id=cc.b2c_event_replication_granular.htm&release=264.0.0&type=5 "The B2C Commerce system fires granular replication events when the granular replication job completes, partially fails, or fully fails. Granular replication operates at the per-object level (products, price tables, content assets) rather than the bulk replication-process level, so its events report which individual object IDs succeeded and which failed.").