Repeat Automations can be configured on both Contact and Transaction Automations.
When enabled, Repeat Automations:
Repeat schedules can be configured as:
Monthly scheduling support may be added in a future update.
Navigate to Automations and create or edit an automation.
Repeat Automations are available in:
Scroll to the Automation Behavior section.
Locate the new option:
Repeat Periodically
Repeat Automations currently require Enroll Existing to be enabled.
Once enabled, Repeat Periodically becomes available.
Open the Repeat settings drawer and configure the schedule.
Available options include:
Weekly and Bi-Weekly schedules additionally require:

Important: Repeat Periodically only functions when Enroll Existing is enabled.
Repeat Automations and Stop on Reply cannot be enabled simultaneously.
If Stop on Reply is enabled:
If Repeat Periodically is enabled:
Repeat Automations do not support Delay Actions.
If an automation contains a Delay Action:
If Repeat Periodically is enabled:
Repeat schedules run according to the configured cadence and the team’s timezone.
Supported schedules include:
Requires:
Requires:
Requires:

All scheduled repeat times are based on the team's timezone.
Communication actions such as Email and SMS continue to respect:
Repeat Automations introduce a new automation behavior: records may exit and later re-enter the same automation.
Before each repeat cycle runs, the system performs a fresh check against the automation’s entry conditions.
If the record still matches the entry conditions:
If the record no longer matches:
If the record matches again later:
This provides flexible automation control without requiring manual enrollment management.

A team creates a recurring automation for referral partners using:
If a partner goes on vacation or temporary leave:
When the partner returns:
The record will resume receiving future repeat cycles once entry conditions match again.
Repeat Automations introduce a new automation status:
On Repeat
Records enrolled in a Repeat Automation may display the On Repeat status even if the automation is currently active or has already completed its initial run. This indicates that the record remains associated with the automation for future scheduled repeats.
Only one automation instance is displayed on the record, even when multiple repeat cycles occur.
Repeat schedules can be modified after an automation is active.
If scheduling settings are updated, such as:
The existing repeat schedule is automatically canceled and replaced with a new schedule using the updated configuration.
This applies whether the new schedule increases or decreases the interval.

Changes to repeat scheduling take effect automatically. Future cycles will use the updated configuration.
When a Repeat Automation is:
Any future repeat schedules are automatically canceled. This helps prevent inactive or orphaned repeat workflows from continuing to run.
Repeat Automation settings are supported within Playbooks. When creating automations from the Playbook Library, users will be able to:
Repeat settings also appear in the Playbook preview.
Repeat behavior varies slightly between Campaign and Workflow automation modes.
Records that are updated to match entry conditions after the automation is active may still enter the automation.
Campaign automations behave differently.
Only records included during the automation’s initial enrollment run can participate in future repeat cycles.
Records updated to match conditions later will not be added to the campaign.
However, records already included in the initial campaign enrollment can:

The Campaign vs Workflow Behavior section only applies to enterprises that have Campaign vs Workflow functionality enabled.
If your enterprise does not use Campaign vs Workflow, Repeat Automations will follow the standard automation behavior described above.

Repeat Automations re-evaluate entry conditions before every scheduled cycle.
This allows records to temporarily stop participating and later resume without rebuilding the automation.
Need more help? Check out: Intro to Automations