Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RollupJob error: Cannot have more than 10 chunks in a single operation #51

Closed
dcarter opened this issue Jul 22, 2014 · 7 comments
Closed
Labels

Comments

@dcarter
Copy link

dcarter commented Jul 22, 2014

"First error: Cannot have more than 10 chunks in a single operation. Please rearrange the data to reduce chunking."

My scheduled rollups (there are several) include (filtered) counts of Assets rolled up to Entitlements, and then (filtered) counts of Entitlements rolled up to Accounts.

From a little Googling, it appears that the usual suggestion when encountering this is to ensure that different types in SObject are sorted in order by type, to minimize breaks/switches between types. For example:
http://sfdcmaniac.blogspot.com/2013_10_08_archive.html

@afawcett
Copy link
Collaborator

I have tracked down a stack dump for this...

Class.dlrs.RollupService.Updater.updateRecords: line 579, column 1
Class.dlrs.RollupService.UpdateWithoutSharing.updateRecords: line 598, column 1
Class.dlrs.RollupService.updateRecords: line 563, column 1
Class.dlrs.RollupService.processScheduleItems: line 308, column 1
Class.dlrs.RollupJob.execute: line 48, column 1

I "think" it will be something we can workaround in the code.

@sethstone
Copy link

+1

lukeadair referenced this issue in lukeadair/declarative-lookup-rollup-summaries Jan 7, 2015
Added test case for 10 chunks during database operation:
SFDO-Community#58
lukeadair referenced this issue in lukeadair/declarative-lookup-rollup-summaries Jan 7, 2015
Bug fix for case when masterRecords contains more than 10 chunks:
SFDO-Community#58
@sethstone
Copy link

Hi Andy, my co-worker @adair21 submitted a pull request that fixes this issue and provides a test case. This is a super-critical fix for us, so I was wondering if you have any plans to build a new package soon. (We currently have DLRS installed as managed package in our Sandbox and Production environments).

Also, one note on the pull request (#104) we pulled out the permission sets that wouldn't deploy and accidentally committed that file. The pull request includes both the change and the revert of the change - sorry about that. Perhaps github allows for cherry-picking from a pull request?

@afawcett
Copy link
Collaborator

afawcett commented Jan 9, 2015

Wow thanks guys! Will take a look and yes will get a release out asap.

afawcett added a commit that referenced this issue Jan 9, 2015
@afawcett
Copy link
Collaborator

afawcett commented Jan 9, 2015

Fantastic work, create test as well, thanks for the contribution! 👍

@afawcett afawcett closed this as completed Jan 9, 2015
@afawcett
Copy link
Collaborator

afawcett commented Jan 9, 2015

@adair21 do you have a Twitter handle?

@lukeadair
Copy link
Contributor

Yes, although I never use it. It's @jlukeadair.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants