We are having some issues introduced by one package from Eloqua, the app was upgraded automatically and it has caused a couple of serious issues.

Is there a way to block this automatic upgrades and 'approve' them or have the choice to do it manually?. Or should we ask Eloqua to exclude our org from those automatic pushes?

Attribution to: PepeFloyd

Possible Suggestion/Solution #1

I haven't tried this, but perhaps you could set a recurring Apex schedule task to run that does nothing but access an object in the package, or somehow connects to another aspect of it. I know that if you have scheduled Apex who's code is contained in a package, that the package can't upgrade until you stop the scheduled Apex.

Might be worth a shot.

EDIT:

Per kibitzer's suggestion, I'd go to Name|Setup|Develop|Apex Classes and look for the Security link next to any class that belongs to the Eloqua package:

These classes are global and if referenced by a scheduled class, this should prevent them from doing a push-upgrade.

Attribution to: Adam
This content is remixed from stackoverflow or stackexchange. Please visit https://salesforce.stackexchange.com/questions/3780