Salesforce workload

Disabling automation and rules during Salesforce record restores

When restoring Salesforce records, you can choose to temporarily disable automation and rules during the restore job. This helps prevent Salesforce business logic from blocking records, triggering unwanted updates, sending emails, or interfering with the restore process.

What is disabled during a restore?

When the Disable automation and rules during restore option is enabled in the restore flow, Keepit temporarily suspends supported automation and rules before the restore begins and automatically reactivates once the job finishes.

The restore works against your current production org configuration, not the snapshot being restored. This means any supported rules or automations that exist today, including items created after the snapshot was taken, are included during the restore process.

The following Salesforce components are supported:

Type

Restore behavior

Validation Rules

Disabled to prevent validation failures

Workflow Rules

Disabled to prevent unintended updates, tasks, or emails

Process Builder (visible in Flows)

Disabled during restore

Flows (record-triggered and autolaunched)

Disabled during restore

Assignment Rules

Disabled to prevent unintended ownership changes

Escalation Rules

Disabled to prevent escalation of restored records

Duplicate Rules

Disabled to prevent duplicate-related insert failures

Auto-response Rules

Disabled to prevent email notifications

Apex Triggers

Temporarily disabled when supported by Salesforce APIs

Disabling automation and rules during Salesforce record restores

All supported items are automatically reactivated after the restore job completes.

Managed package limitations

Due to Salesforce API limitations, this type of restore cannot disable:

  • Managed package Flows
  • Managed package Apex triggers

These items remain active during the restore job. If they could affect your restore, we recommend disabling them manually in Salesforce before starting the restore.

Any managed package items detected during the restore are included in a downloadable CSV report found in the Job monitor. 

Developer Edition org considerations

Developer Edition orgs used for managed package development may not behave consistently due to Salesforce namespace-related API limitations.

If you are restoring into one of these orgs, we recommend manually handling rules and automations directly in Salesforce before running the restore job.

Error handling and notifications

If rules or automations cannot be disabled before restore

The restore job will not proceed and will be marked as unsuccessful. You'll receive an in-app message and email alert.

To see which automations could not be disabled and why, download the CSV from the job report in the Job monitor.

To continue, either retry the restore or manually disable the rules and automations in Salesforce before running it again.

If rules or automations fail to reactivate after restore

The selected items will be restored, but the job will be marked as incomplete. You'll receive an in-app message and email alert.

To see which automations failed to reactivate and why, download the CSV from the job report in the Job monitor.

To reactivate manually, use the CSV to identify the affected automations and reactivate them in Salesforce.

If selected items fail to restore

The restore job will be marked as unsuccessful. Keepit will still attempt to reactivate any rules or automations that were disabled.

Disabling automation and rules helps reduce the risk of Salesforce automation interfering with restore jobs while minimizing the need for manual pre- and post-restore administration.