Since Winter '15 it has been possible to deploy Apex classes even when they are actively scheduled 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.

I recently noticed that this only seems to work when using the Metadata API -- when I switch my IDE (MavensMate running on Atom) to use the Tooling API, I start to get these errors again.

Is this the expected behavior or a bug with the Tooling API in my org? If this is the expected behavior, has anyone seen signals from SF on whether they will update the Tooling API to match this behavior? Seems like the kind of thing that should be consistent across tools...

  • I ran into the same situation with Mavensmate. I deploy the code to the same org using the mavensmate deploy option and it works. – javanoob Feb 6 '17 at 18:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.