aheber
commented
1 month ago @reaganh17 can you report the DLRS version that you are using as well as the rollup configuration you are using?
Do you only have a single rollup or multiple?
Are you able to reproduce this in a minimal org ( a fresh developer edition or scratch org?) or just in your company production or sandbox orgs?
The most important thing will be collecting enough information that we, as a developer team, can replicate this behavior and find the root cause.
Describe the bug When attempting to rollup to BenefitSession as the parent object, performing a full calculate or scheduled flow will cause it to hang forever, even when running it on a single record (with just 1 child record for testing). This is not the case for all NPC objects, as BenefitAssignment can be a parent object without issue. BenefitSession can also be a child object and rollup just fine. Real-time mode works as well, it just fails on full calculate/scheduled. Also note that using a scheduled flow and calling the rollup with BenefitSession as the parent works as well.
To Reproduce Create a rollup with BenefitSession as the Parent, BenefitAssignment as the Child. Rollup a Count of Id, perform a full calculate on a single BenefitSession record. Apex Jobs will show it in Processing mode forever. Scheduled rollups will fail as well since it's trying to process the job but never succeeds, giving an error that the same rollup is already processing.
Expected behavior This should be a simple rollup counting the child records.