Queued Apex Jobs on RollupAsyncProcessor

[jkenzer]

@jamessimone Question for you. Is it normal and expected behavior that there are constantly running Queued and Processing Apex Jobs on the RollUpAsyncProcessor. I ran a full recalculation via CMDT on Friday afternoon and now I'm seeing this behavior non-stop since.

[jamessimone]

That is definitely not expected. Let me take a look at what might be causing that and get back to you.

[jkenzer]

@jamessimone Thanks for the code. I deleted them all out and then ran a full recalculate in my sandbox again to see if I got the same results. I do get the same behavior. Do you want me to submit this as an issue and if so, what other kind of support can I provide?

[jamessimone]

@jkenzer feel free to raise an issue for this - I am also adding in additional logging and potentially some other speculative changes that may solve this; either way, we'll get it sorted out with either the logs or the changes I'm planning to make.

[jamessimone]

@jkenzer in the latest release, there are additional logging statements that may help to clarify why rollup is continually re-running for you. Let me know if you want some help poring through them!

[jkenzer]

@jamessimone I just encountered this issue again with the latest release trying to do the initial populating on a new rollup. What should I look for in the logs to help determine what's going on?

[jamessimone]

@jkenzer I added some logging statements that you should see if you have your Is Rollup Logging Enabled checkbox set to true on the Org Default for RollupControl__mdt - things like Number of deferred rollups (#), still allowed to requeue? and so on. Hopefully there's enough information in those messages to determine what is causing this endless re-queue scenario.