#1 Global Leader in Data Protection & Ransomware Recovery

CANNOT_EXECUTE_FLOW_TRIGGER. You or your organization has exceeded the maximum limit for this feature.

KB ID: 4367
Product: Veeam Backup for Salesforce | 1.0 | 2.0 | 2.1
Published: 2022-10-27
Last Modified: 2023-08-30
Languages: DE | FR
mailbox
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.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

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:

  1. Open Configuration
  2. Navigate to "Product Settings"
  3. Switch to the "Advanced Settings" tab.
  4. Note the current value for sf.composite.batch.size
    The default is 200.
  5. 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.
  6. Perform the records restore.
    If the restore fails with the same error, reduce the sf.composite.batch.size value further.
  7. After the successful restore, revert the sf.composite.batch.size value to what was observed in Step 2.

 

 sf.composite.batch.size
In Veeam Backup for Salesforce 1
VBSF v2
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. 
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.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.