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.

Sign up for GitHub

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

Jump to bottom

RollupAsyncProcessor for job ID 707VI00000pPWLK. : Too many query rows: 50001 #625

Closed
baobao917 opened this issue Sep 19, 2024 · 2 comments
Closed

RollupAsyncProcessor for job ID 707VI00000pPWLK. : Too many query rows: 50001 #625

baobao917 opened this issue Sep 19, 2024 · 2 comments

Comments

@baobao917
Copy link

I've gotten these errors from time to time and do not know what it pertains to or how to resolve.

image
jamessimone added a commit that referenced this issue Sep 26, 2024
@jamessimone
Attempted fix for #625 - do not allow max query rows to exceed the pl…
778f026 
…atform limit
@jamessimone jamessimone mentioned this issue Sep 26, 2024
Merged
jamessimone added a commit that referenced this issue Sep 26, 2024
@jamessimone
v1.6.34 - Bugfixes! (#628)
91dfd99 
* Removes GAP_CREATE and GAP_UPDATE from CDC handling as those are not valid CDC cases for rolling up

* Fixes an issue with the Rollup_Field_Parent_Required validation rule on Rollup__mdt

* Fixes #619 by more carefully handling parentRecordIdForEmptyChildrenCollections variable

* Updates jsconfig.json with new CLI-based changes

* Removes heap size checks as they are unncessarily expensive when checking rollup limits

* Fixes #626 by patching a few places where RollupControl__mdt being null (which is sometimes set internally by the framework for performance reasons) does not cause issues when trying to log

* Fixes #623 by properly parsing nested IN conditions during recursive where clause operations

* Fixes #622 by properly tracking changes to calc items when updates occur with differing values for multicurrency orgs

* Fixes an issue where sync rollups enqueued by Flow would not run in the proper order

* Attempted fix for #625 - do not allow max query rows to exceed the platform limit


* Fixes an issue reported by Katherine West where multiple order bys were sometimes omitted in RollupRepository queries due to an inner ordering - moved the ordering to in-memory sorting
@jamessimone
Copy link
Owner

@baobao917 I've put in a potential fix for this in the latest version. I'll hold off on closing this until you're sure this is working, though.

@baobao917
Copy link
Author

Hi @jamessimone - Thanks for the update. I'm not really sure how to reproduce the error as it just sort of happens from time to time. You can close this issue and if it pops up again, I can just open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jamessimone @baobao917