Developer script exception from Vacatia : Error processing finalizer for queueable job id: 707Vo00001JiKvN : Cursor Rate Limiting Exception : DailyApexCursorRowsLimit Limit exceeded.

[manilaagnihotri11]

Getting below error and since this has been esclated I need your urgent support @jamessimone
Apex script unhandled exception by user/organization: 005Vo00000ZZWgn/00D8c000002goUh

Organization: Vacatia (vacatia.my.salesforce.com).

Error processing the finalizer (class name: RollupFinalizer) for the queueable job id: 707Vo00001JiKvN (queueable class id: 01pVo000000rZkQ)

caused by: System.LimitException: Cursor Rate Limiting Exception : DailyApexCursorRowsLimit Limit exceeded.

Class.RollupRepository.getCursor: line 54, column 1
Class.RollupFullBatchRecalculator.CursorBasedRetriever.: line 95, column 1
Class.RollupFullBatchRecalculator.startAsyncWork: line 63, column 1
Class.RollupAsyncProcessor.beginAsyncRollup: line 505, column 1
Class.RollupAsyncProcessor.runCalc: line 281, column 1
Class.RollupFinalizer.recurseThroughConductors: line 64, column 1
Class.RollupFinalizer.execute: line 37, column 1

[jamessimone]

This is an open source project of mine; I don't have an SLA or timeline for responding. You seem to be reporting an issue related to limits specific to your org. Apex Rollup should not create so-called "runaway" jobs - it should only create cursors (and use up Apex Cursor Rows) as required to meet the needs of your rollups, and typically full recalculations are only performed once - during initial setup, to sync values up with the rollups you've configured.

I know (from information that you haven't shared here, but was shared with me on Discord) that you have an integration user that bulk updates records within this org. It sounds like rollups were configured without testing that path. My advice to you would be to:

• write unit tests that validate that something like your integration user receiving bulk record updates successfully rolls up to the records in question without going into full recalc mode (as I've never heard of that happening before)
• enable the Is Rollup Logging Enabled flag on the Org Default Rollup Control record, have whatever integration you're doing perform a bulk update, and observe the logs that are created

[manilaagnihotri11]

@jamessimone - The job is getting called from each user and not from a integration user.

[jamessimone]

@manilaagnihotri11 I would perform some testing, in that case. You're also exposing PII in that screenshot, unless that's a test user name.

[manilaagnihotri11]

@jamessimone - Let me know if we can connect or how do you want to debug it.