Troubleshoot an Abort

Learn why an abort request can fail and how to check that a job chain stopped.

Step 1 Returns 404

You can abort a job chain worker only while it is starting or running. If the worker is stopping or already stopped, there is nothing to abort. Step 1 then returns the status 404.

Step 1 returns these fields.

Field	Description
`k8sJobId`	The Kubernetes job identifier of the job chain worker. Pass this value to step 2.
`jobState`	The state of the job chain worker.
`launchId`	The identifier that the system assigned when the job chain worker started.

Step 2 Returns 404

The job no longer exists. It might have ended after you ran step 1.

Step 2 Fails Without a Clear Error

Check that the key in the map you pass to execute() is exactly k8sjobid. If the spelling or case differs, the path variable is not replaced.

Check That a Job Chain Stopped

A running job chain worker updates the Last_Update_Date__c field of its Batch Run Status records about once a minute. After an abort, these records keep their last Batch_State__c value, but Last_Update_Date__c stops changing.

If a record shows Running and its Last_Update_Date__c has not changed for much longer than a minute, the system is no longer processing it. When you schedule new work, a new worker starts and the records update again.