Scheduled jobs never run when created in managed package

Question

I am implementing the InstallHandler interface for a managed package which creates a scheduled job to run. A scheduled job is created when I install the package, with a status of Queued. However, the job never seems to run.

However, if I run the exact System.schedule command via anonymous Apex, the job actually gets created and runs properly. This makes me believe that the job creation and underlying code are working properly, but perhaps there is a permissions issue preventing the job from running. So far the only difference I can see is that the user is different for the two methods of creating the job. When installed by the managed package, the Submitted By name is the name of my package, but when I run via anonymous Apex the Submitted By name is my SysAdmin user.

Does anyone have an idea as to why the actual job never runs?

Answer 1

The runtime privileges of the class may be ambiguous.

If you annotate without sharing on the InstallHandler and the Schedulable implementors, that would eliminate one source of possible problems.

After that, it would be a great post-mortem followup to find out which particular part of the install handler or scheduled job happened to be very sensitive to sharing.