Gearset provides the option to temporarily disable any triggers or flows that might interfere with the archival process. Salesforce imposes limits on the number of records that can be modified in a single batch. With triggers or flows enabled, these limits are often further constrained due to chained updates, reducing the number of records that can be archived at once.
Configuring Deactivation and Reactivation
This can be configured in any policy at the automations step. Once everything is else configured and you reach the automation tab.
In cases where Gearset detects triggers or flows that could affect the deployment, it will populate them for you to review and select, allowing them to be temporarily disabled during the run.
If there aren't any you’ll see a message confirming that no triggers will be impacted when this policy runs.
These automations are automatically reactivated after the policy has finished running. However, if a failure occurs, you may need to reactivate them manually.
Accessing Deactivation/Reactivation Run History
We also have the ability to roll back deployments by navigating to the specific archive policy, clicking the history, and moving to ‘All Events.’ This view shows all policy runs, including those with disabled/enabled automations.
These runs to deactivate and reactivate will be listed in the history as ‘Disabling/Reactivating Automations for Archiving Job: [Insert Your Job Name Here]’. You can roll them back if the automation that reactivates them fails for any reason.
