Abort Behavior

What an Abort Stops

The sales org you pass to OffPlatformCallout selects the cloud platform that hosts the sales org. The platform is either Amazon Web Services or Google Cloud Platform. The abort applies to that platform, not to a single sales org.

Each tenant has one job chain worker on each platform. There is not one worker for each sales org or for each job chain. When you abort the worker, all job chains of the tenant on that platform stop.

For example, you pass sales org 0001. The abort does not stop only the work of sales org 0001. It stops the job chains of every sales org on the same platform.

If your tenant runs job chains on both platforms, abort each platform separately. Run the two steps once with a sales org on one platform. Then run them again with a sales org on the other platform.

What an Abort Does Not Stop

An abort affects only the job chain worker. These processes run outside the job chain framework and keep running.

• Salesforce data synchronization
• Integration inbound and outbound processing
• Object change handlers

Batch Run Status After an Abort

An abort ends the job chain worker immediately. The worker does not write a final status. The Batch Run Status records of the stopped run stay in their last state. For example, a record can still show Running. This is expected.

To learn how to change these records, see Update Batch Run Status Records After an Abort.

Scheduling After an Abort

To resume work, schedule a job in a new job chain. This starts a new job chain worker. The new worker runs the newly scheduled jobs as usual.