Salesforce "Your deployment has been aborted" in CI

By Kaveh Alemi·Latchkey

The deploy did not run its components to a result; it was aborted. This happens when a deployment is cancelled, when another deploy takes over the org's deploy slot, or when the CLI cancels a long-running request.

What this error means

The deploy ends with "Your deployment has been aborted" rather than a pass/fail component report. Nothing was committed to the org.

Status: Aborted
Your deployment has been aborted.

Common causes

A concurrent deployment took the slot

Salesforce processes one deployment at a time per org. A second job (or a manual deploy) can abort or block another running against the same org.

The CLI cancelled the deploy

A deploy cancel, a job timeout, or a cancelled CI run aborts the in-flight deployment.

How to fix it

Serialize deploys to the same org

1. Ensure only one CI job deploys to a given org at a time (use a concurrency group).
2. Wait for an in-progress deploy to finish before starting another.
3. Re-run the aborted deploy once the org is free.

concurrency:
  group: deploy-${{ github.ref }}
  cancel-in-progress: false

Check for and let running deploys finish

Query in-progress deploys and avoid starting a new one until the org is idle.

sf project deploy report --target-org ci-org

How to prevent it

• Use a concurrency group so only one deploy hits an org at once.
• Avoid manual deploys while CI is deploying to the same org.
• Give deploys enough job time so they are not cancelled mid-flight.

Frequently asked questions

Related guides

References

• GitHub Actions documentation