James Simone
James Simone
@mmablom this was fixed (as well as it can be, currently) with #707. I am pushing teams internally to fix the underlying CMDT query performance
@mmablom believe me, I hear that! Best of luck with your endeavors
Hey there, Just looking at that select statement for your schedule, there's nothing obviously wrong with it, other than that it probably is quite a large amount of records to...
@jithishakn is your `Should Skip Resetting Parent Fields` checkbox true on your rollup control record? As far as I can tell, that's the only way that the older records which...
@jithishakn I've been doing some testing to try to reproduce the issue you're describing, including setting up a scheduled flow and a number of different comma-separated rollups to be invoked...
@jithishakn my recommendation would be to: * enable logging on the Org Default Rollup Control CMDT record * optional, but very helpful: if you don't already use [Nebula Logger](https://nebulalogger.com/), install...
I am closing this issue - the fact that the rollups were working in UAT but not production is a strong indicator (to me) that there are dueling automations at...
Thanks for the details, I will take a look!
@simoneduckworth I made some change to the way that full recalculations chain over the past few versions - is this issue still happening?
What version of Apex Rollup are you on? And is the log being generated from an instance of `RollupFullBatchRecalculator` ? Or is it an instance of `RollupDeferredFullRecalcProcessor` ? It's OK...