You can abort a database ingestion and replication job that is in the Up and Running, On Hold, Running with Warning, or Stopping state.
For an incremental load job, the job stops immediately after a checkpoint is taken. A checkpoint records the point in the change stream where incremental processing left off for recovery purposes.
For a combined initial and incremental load job, any running initial load subtasks stop immediately. For the incremental load portion of the job, a checkpoint is taken and then the job stops.
For an initial load job, any running subtasks stop immediately and then the job stops. Non-running subtasks remain in their current states.
1Navigate to the row for the job that you want to abort in any of the following monitoring interfaces:
- My Jobs page that's accessed from the navigation bar of the Home page
- All Jobs page in the Monitor service
- All Jobs tab on the Data Ingestion and Replication page in Operational Insights
2From the Actions menu for the job, select Abort.
The job state switches to Aborting and then to Aborted.
For initial load jobs, the state of started and running subtasks switches to Aborted. For incremental load or combined initial and incremental load jobs, the state of subtasks switches to Stopped.