CANNOT_EXECUTE_FLOW_TRIGGER. You or your organization has exceeded the maximum limit for this feature.
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Oops! Something went wrong.
Please, try again later.
Challenge
When performing a restore involving multiple records, one or more records fail to be restored with the following Salesforce error message:
CANNOT_EXECUTE_FLOW_TRIGGER. You or your organization has exceeded the maximum limit for this feature. Error ID: XXX-XXX (XXX) organization has exceeded the maximum limit for this feature.
Cause
The record creation or update in Salesforce triggers automation flows that violate the Salesforce platform limits.
Solution
To work around this issue, reduce the batch size for the duration of the restore operation. To do this:
- Open Configuration
- Navigate to "Product Settings"
- Switch to the "Advanced Settings" tab.
- Note the current value for sf.composite.batch.size
The default is 200. - Modify the value for sf.composite.batch.size to a lower number.
The exact value this must be lowered to is different for every environment. Consider 100, half-default as a starting point. - Perform the records restore.
If the restore fails with the same error, reduce the sf.composite.batch.size value further. - After the successful restore, revert the sf.composite.batch.size value to what was observed in Step 2.
In Veeam Backup for Salesforce 1
In Veeam Backup for Salesforce 2
More Information
Note from Veeam Product Management:
The error documented in this article may occur even when you have a small number of automation rules in place or a small or empty trigger that you have created yourself. Each managed package installed in your Salesforce Org may bring its own triggers and workflows. Salesforce will not fail during the execution of the managed package code but will produce an error immediately after the code execution when Salesforce begins processing the automation flows.
The error documented in this article may occur even when you have a small number of automation rules in place or a small or empty trigger that you have created yourself. Each managed package installed in your Salesforce Org may bring its own triggers and workflows. Salesforce will not fail during the execution of the managed package code but will produce an error immediately after the code execution when Salesforce begins processing the automation flows.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.