Job and Object Statuses (Edge)
Edge Pipeline is currently available under Early Access. You can request access to evaluate and test its features.
Based on the replication and error-handling settings configured for the Pipeline, a job may progress through the following stages and statuses. Refer to the Object Statuses section below for object-level statuses.
Job Statuses
The following diagram illustrates the different statuses that may be assigned to a job through the data replication process. These are explained in the table below it.
If you find any object with failed Events in the job details, you can restart the object using the Restart Now or Run Now action. This creates a Historical job with just that object.
| Job Status | Description |
|---|---|
| In progress | The job is created and objects are being processed. |
| Completed | The job completed successfully and the ingested Events are loaded to the Destination. |
| Completed with Failures | The job is completed but one or more objects has failed Events. |
| Failed | One or more Source objects have failed, and: - Either the configured behavior is Strict, or, - The cofigured behavior is Moderate but the overall limit of 10K failed Events is crossed. |
You can restart a failed object using the Restart Object action in the Job Monitoring view. This creates a Historical job with just that object.
Object Statuses
The following diagram illustrates the different statuses that may be assigned to the object across the data ingestion and loading stages. These statuses are described in the table below it.
| Object Status | Description |
|---|---|
| Not Initialized | The job is created but not yet started. This may be because another job is curently running. |
| In progress | The replication of Events is in progress. Till the ingestion stage completes, the load stage remains in not-initialized state. |
| Completed | The ingestion for the object is done for the current batch, offsets have been updated, and the object is loaded to the Destination. |
| Completed with Failures | The object is processed but one or more Events had failures during ingestion or loading. |
| Failed | The ingestion or loading of Events has failed, and: - Either the configured behavior is All or None, or, - The cofigured behavior is Partial Load but the batch failure threshold was breached. |