---
title: Prevent repeat enrollments
description: Read and understand the re-enrollment timeout on a trigger, which stops the same employee being enrolled again when data changes or a trigger fires twice.
sidebar:
  order: 2
area: flows
feature: automations
appPath: /flows/home
lastVerified: 2026-10-22
version: "2026-10-16"
audience: admin
related:
  - flows/automations/trigger-catalogue
  - flows/automations/scheduling-internals
  - flows/automations/move-an-enrollment-to-a-new-start-date
---

Every trigger carries a re-enrollment timeout. When a trigger fires for someone who has already been through the automation, Pyn compares the time since their last enrollment with the timeout and skips them if it is too soon. This is what stops a corrected start date, a re-synced manager or a second form submission from sending the whole sequence twice.

## Before you start

- The setting lives on the trigger drawer's **Advanced** tab as **Prevent repeat enrollments**. Its description reads "Prevents an employee from being enrolled again for a period of time, e.g. when data is changed or corrected. Date and property triggers wait at least a day."
- Pyn sets a default per trigger and the field is read-only in most workspaces. Contact support@pynhq.com to change a timeout.

![Advanced holds the re-enrollment timeout for the trigger.](https://support.pynhq.com/media/flows/automations/flows-automations-trigger-advanced.png)

## Steps

1. In Pyn, open **Flows** in the left navigation, then **Automations**, and select the automation.

2. Select the trigger card, then the **Advanced** tab.

3. Read the value under **Prevent repeat enrollments**. The options are **Always reenroll**, **1 hour**, **1 day**, **2 days** through **7 days**, **1 month**, **3 months**, **6 months**, **12 months** and **Never reenroll**. Date and property triggers hide **Always reenroll** and **1 hour**, because they are re-evaluated several times a day.

4. If your workspace can edit the value, choose a new one and select **Publish**.

## Defaults by trigger

| Trigger | Default |
| --- | --- |
| Will be joining, Pre-onboarding, Start of Onboarding | Never reenroll |
| Off-boarding, Upcoming Anniversary, Upcoming Milestone Anniversary, Birthday (template), date properties | 1 month |
| Buddy Assigned, Promoted to Manager, Change of Manager, Group Change, Change of Location, Connected to Slack | 1 month |
| Recurring Trigger | 1 day |
| Form Submission, Custom trigger | Always reenroll |
| Employee Property (text or yes/no), No trigger | Never reenroll |

> **Note:** Manual Enroll has its own guard: the same person cannot be enrolled in the same automation twice within five minutes, unless **Flag as Test** is on. The trigger's timeout does not apply to manual enrollments.

## What you should see

An employee who re-matches inside the timeout does not get a new row under [Enrollments](https://support.pynhq.com/activity/enrollments/). With **Never reenroll**, a person who has been enrolled once is never enrolled by the trigger again, including a rehire. To run them through again, use **Manual Enroll**.

## Related

- [Trigger catalogue](https://support.pynhq.com/flows/automations/trigger-catalogue/) for every default.
- [Scheduling internals](https://support.pynhq.com/flows/automations/scheduling-internals/) for the one-day minimum on polled triggers.
- [Move an enrollment to a new start date](https://support.pynhq.com/flows/automations/move-an-enrollment-to-a-new-start-date/) for what to do when a date changes.