Deploy with Active Jobs

An option has been added to the Deployment Settings page that lets you deploy components referenced by active Apex jobs. With this option, you don’t have to cancel Apex jobs to be able to have a successful deployment.

Previously, deployments failed if they contained components that were referenced by Apex jobs that were pending or in progress. For example, if you deploy an Apex class that implements Schedulable, and there is a scheduled job that corresponds to this class, this class can’t be deployed, and the entire deployment fails.

You can now enable the deployment of components with corresponding jobs—including scheduled jobs, batch jobs, and future methods—and avoid deployment failure. To do so, from Setup click Deployment Settings | Allow deployments of components when corresponding Apex jobs are pending or in progress, and then click Save.

As part of this change, the Deployment Connections page has been renamed to Deployment Settings.

This option applies to change sets and deployments started through the Metadata API.

Note

Note

  • Enabling this option might cause Apex jobs to fail due to unsupported changes.
  • This option doesn’t affect editing and saving Apex code in the Salesforce user interface (in Setup or the Developer Console), which will fail if there are active jobs associated with the Apex class. Updating Apex code by using the Force.com IDE can succeed if this option is enabled because Metadata API is used for the code update.