Next Scheduled Run empty when using System.scheduleBatch in managed package

Question

I'm trying to debug this recent issue. Code works fine in scratch orgs, but when ran in managed package scheduleBatch seems to never execute. I wonder if there's some throttling going on as we use this mechanism to chain batch jobs (although this happens on very first use of method, not far into chain).

Is there some ways to debug this (can't see our own logs, ugh.)

Edit: adding some screenshots. Note after Next Scheduled Run the CronTrigger.State changes to deleted. No debug log gets generated 🤷‍♂️

Answer 1

You can do Troubleshooting in Subscriber Organizations. When you Log In to Subscriber Orgs from a License Management App-enabled org, you can either use the ISV Customer Debugger or you can get ISV-only logs from the Developer Console. You'll need to Request Login Access from a Customer before you can use these features, however.

In general, there is no additional throttling that happens when scheduling jobs, but do be aware that the Execution Governors and Limits restrict an org to 100 scheduled jobs in total (including Scheduled Batchable jobs). Make sure you're not exceeding these limits. You should be able to use a try-catch block to detect when this situation occurs:

try {
  System.scheduleBatch('jobName',new BatchableClass(), minutesFromNow);
} catch(AsyncException e) {
  // Can't schedule job for some reason
} catch(StringException e) {
  // Invalid job name, etc
}

Answer 2

In order to get logs from a subscriber org containing info from your package's Apex you need to make sure you:

1. Gain login access for your "support" (request login access and have it granted).
2. Login via your PBO's Subscribers tab.
3. Create a new User Trace Flags through Setup > Environments > Log > Debug Logs (this must be done using the subscriber login grant), making sure to provide adequate time coverage for your needs and using a "log type" that has debug, fine or better Apex tracing.
4. Execute the required processing on the subscriber org with whichever user you set up the trace flags for.
5. Open the Debug Log using the same login as step 2.

As long as you follow these steps appropriately you will be able to get unobfuscated and detailed logs from your package on the subscriber org.

It should be noted that you might be bumping into this issue and I would encourage you and your team mates to upvote it to help get this problem resolved.