Hi!
I have an org in which I created a DLRS roll-up based on real-time, but then moved to 'watch and process later' but it's messing with a flow that I have running. The flow is record triggered, and on a scheduled path to wait 30 minutes. With the roll-up happening over-night I don't feel like it should be affecting my record triggered flow, but this is the error I'm getting even on a batch of 2 records (when an import happens):
Error Occurred: The flow tried to update these records: 006Rz00000WgqLVIAZ. This error occurred: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: dlrs_OpportunityTrigger: execution of AfterUpdate caused by: System.DmlException: Upsert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record or 1 records: a1aRz000006lTxZIAU: () (dlrs) Trigger.dlrs_OpportunityTrigger: line 7, column 1. You can look up ExceptionCode values in the
SOAP API Developer Guide.---
Is it possible that the trigger is still running on real-time? I can see in the scheduled jobs that the jobs are running at the allocated overnight time (I have 3 DLRS roll-ups in this org)
If so, what's the best way for me to deal with that trigger? OR any other suggestions here for what I'm (not) seeing.
Thanks!
Invocable by Automation is the "I'm going to tell you when to run" option. It bypasses DLRS' "watch these records" and takes over things on your own.
If you're driving by Flow, or using Scheduled Recalculation then that is exactly what you're looking for.
There is a DLRS Invocable Action available to kick off recalculation. You give it a Rollup Name as well as the Parent Ids that should be recalculated. (If I'm remembering correctly.)
