-
Notifications
You must be signed in to change notification settings - Fork 238
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
System.TypeException: Cannot have more than 10 chunks in a single operation. #168
Comments
This might be a similar to this issue, are you running the latest version of the package? |
Thanks Andy. We were on 1.13. I am upgrading to 1.19 and will re-test. If all checks out, I will close this issue. Thanks again. |
Any luck @alan-birchenough? |
Sorry - I have not been able to get the instructions to reproduce from the person Thanks for the reminder, On Sat, May 23, 2015 at 8:32 AM, Andrew Fawcett [email protected]
|
I have been able to confirm that this was fixed by the upgrade to 1.19. Thanks for your patience. Regards, |
Awesome thanks! |
We are using additional roll-up triggers on our PSA Project Tasks to roll up totals to Iterations amongst other things.
A colleague was performing a story clone (a large-scale deep clone of stories from one project to another), and received the following error:
Apex script unhandled exception by user/organization: 005U0000000IVbz/00DU0000000JBB3
Visualforce Page: /apex/CloneStoriesFromTemplate
caused by: System.DmlException: Insert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, dlrs_pse_Project_TaskTrigger: execution of AfterInsert
caused by: System.TypeException: Cannot have more than 10 chunks in a single operation. Please rearrange the data to reduce chunking.
(dlrs)
Trigger.dlrs_pse_Project_TaskTrigger: line 7, column 1: []
It seems we may be indirectly invoking DLRS in such a way as to cause sub-optimal chunking, but we're not sure how to change our approach so as to improve the situation. Any guidance on chasing this down would be gratefully received.
The error is in our production org, not a client's, so we should be able to reproduce this at the drop of a hat, and get access to logs, etc.
Thanks in advance for your advice.
The text was updated successfully, but these errors were encountered: