Hello,
I am looking for some support on how to review and manage the error messages I am receiving related to the DLRS jobs I currently have scheduled that seem to be 'bumping' into each other.
The two error messages (related to different scheduled jobs) I am receiving are:
1. Error: A calculate job for rollup 'XXX' is already executing. If you suspect it is not already running try clearing the applicable record from the Lookup Rollup Calculate Jobs tab and try again. Review the error, rollup definition and/or delete the Apex Scheduled job under Setup. Check if the rollup still exists via the Manage Rollup Summaries and/or Lookup Rollup Summaries tabs.
2. Error: You've exceeded the limit of 100 jobs in the flex queue for org XXX (sandbox). Wait for some of your batch jobs to finish before adding more. To monitor and reorder jobs, use the Apex Flex Queue page in Setup. Review the error, rollup definition and/or delete the Apex Scheduled job under Setup. Check if the rollup still exists via the Manage Rollup Summaries and/or Lookup Rollup Summaries tabs.
We have multiple jobs that are scheduled to run on the Opportunity spaced out by 30min but I did also receive error message 1. for a job that is scheduled on the Contact and Tribute.
When I review the Lookup Rollup Calculate Jobs, I see 14 jobs with created dates in the past (12/31/2025 and 01/01/2026). I have deleted these and will wait to see if they show up again after the nightly scheduled jobs run.
The Apex Flex Queue looks to have quite a few that are all related to RollupJob from 12/31/2025 and 01/01/2026.
Any suggestions to try or ideas on how to fix this would be greatly appreciated!
maybe I'm missing the point but I don't see your product or comment as relevant or helpful in this situation. Please be more careful before spamming old posts trying to generate business. This thread hasn't been active since January!
This is a product-specific group and these are product-specific errors (mostly). I don't think adding in an additional unrelated product is going to resolve these concerns I wouldn't want people to get the impression that working with your solution would help if they encounter the same errors.
