Issue
When attempting to update multiple schemas using the Config Migration tool (e.g., from Production to Development), the process may fail with the error message:
“These updates will exceed the maximum allowed time and fail. Try breaking up schema changes into smaller groups.”
This typically occurs when one or more schema changes exceed product-defined limits, preventing the migration from completing successfully.
Resolution
Break Down Schema Changes
- Identify the specific schema changes causing the issue.
- Use the Compare Config functionality in the tool to isolate problematic updates.
- Exclude the problematic schema(s) from the migration:
- Run the migration tool, validate updates, and ignore the problematic schema if dependencies allow.
- Ensure dependent updates are handled separately.
- Retry the migration for unaffected schemas.
Manually Apply Changes for Problematic Schemas
- If excluded schemas still need to be updated:
- Apply the changes directly in the target environment using manual edits or custom scripts.
- Validate the changes in the target environment to ensure they align with the desired configuration.
Product limits typically arise when schema updates require extensive computation, such as registry revalidation. If the changes to be made on a schema cannot be done manually in the UI, reach out to support@benchling.com to help get these made in the target tenant.