Rollups not calculating correctly over time

[baobao917]

Hi @jamessimone - Not sure how exactly to demo this and perhaps it's been resolved with the latest release. But I have noticed that over time the rollup calculations on records aren't 100% accurate. This was noticed in version 1.6.13 and seen occurring in multiple orgs.

Essentially I instituted SUM rollups (both simple parent-child and also grandparent-child) and did a full recalc in the system and verified that the rollup calcs did indeed calculate correctly when comparing to the detail. However, when I checked several months later the rollup calcs, it appeared that many of the target rollup fields did not have the correct result of the sum of the child detail.

I've updated to v.1.6.33 and have done a full recalc again to verify my starting point rollup calculations are correct and I guess I'll observe if it gets thrown out of whack again. But I'm not sure why it would be or how to even begin giving you a starting point to troubleshoot.

[baobao917]

Quick follow-up - As a workaround, since I know the full recalc works, I've thought about doing a periodic weekly full recalc. Is there a way to schedule the full recalc for a particular rollup? I didn't see it in the App

[jamessimone]

@baobao917 you can use a scheduled flow with the Full Recalc CMDT-driven Invocable invocable action - it takes a comma-separated list of the CMDT developer names and runs full recalcs for those rollups

[baobao917]

@jamessimone Thanks! I'll take a look at it.

[baobao917]

@jamessimone I had an issue with using the Full Recalc CMDT driven invocable. I passed a comma separated list of 9 rollups (using the API names) and it's only doing full recalcs on 3 of them. (It's not even the first 3 or last 3 in the list but just smack dab in the middle of the list). Not sure if this is user error on my part or if it's a bug. Also not sure if I should have spawned this off into a separate issue ticket.

Here is a video recording of the issue
https://www.loom.com/share/50814e63ab5d4820870076ae0fe70998

Pls let me know if you need anything else.

[baobao917]

@jamessimone I had an issue with using the Full Recalc CMDT driven invocable. I passed a comma separated list of 9 rollups (using the API names) and it's only doing full recalcs on 3 of them. (It's not even the first 3 or last 3 in the list but just smack dab in the middle of the list). Not sure if this is user error on my part or if it's a bug. Also not sure if I should have spawned this off into a separate issue ticket.

Here is a video recording of the issue https://www.loom.com/share/50814e63ab5d4820870076ae0fe70998

Pls let me know if you need anything else.

@jamessimone I am going to open a separate issue for this issue with the Full Recalc CMDT driven invocable to separately track it from this original issue.

[baobao917]

Hi @jamessimone - Hope all is well. Have you had a chance with this yet?

[jamessimone]

I won't be able to investigate this issue without more details. If you have Apex Rollup triggering on record insert/update/delete, all rollups will be kept in sync!