Released: July 30, 2026
Bolt Agent Jobs now support repeatable enrollments. Until now, once a trigger enrolled a contact in a job, that same trigger would never enroll them again, even after the job finished. With this update, each job trigger has a Repeatable toggle, bringing the repeatable-trigger behavior you already use in Workflows to Bolt Agent Jobs. When Repeatable is on, a contact can be enrolled again after their previous enrollment reaches a terminal state, so a job can respond every time a contact repeats a recurring action such as submitting a new inquiry or opening a new support request. When it is off, jobs continue to enroll each contact only once, with no change to existing jobs.
Repeatable toggle: Each Bolt Agent Job trigger now has a Repeatable setting that controls whether the same contact can be enrolled more than once. It is off by default, so existing jobs keep their current enroll-once behavior. When enabled, enrollment follows these rules:
Non-terminal state: No new enrollment while the contact's current enrollment in the job is still active. Active statuses are Pending, Monitoring, Thinking, Taking Action, Approval Needed, Scheduled, and Error. This prevents overlapping or duplicate runs.
Terminal state: A new enrollment is allowed once the contact's most recent enrollment reaches Goal Completed, No Action Needed, Cancelled, or Abandoned.
Non-repeatable triggers: Triggers left off continue to enroll each contact only once, exactly as before.
Per-trigger control: The Repeatable setting lives on each trigger, so a single job can mix repeatable and enroll-once triggers. Enrollment is evaluated against the contact's most recent enrollment in the job, whichever trigger created it. A repeatable trigger can enroll a contact again once that enrollment is terminal, while a trigger left off will not enroll a contact who has ever been enrolled in the job.
Supported triggers: Repeatable enrollment is available on every Bolt Agent Job trigger.
Trigger-based enrollment: These rules govern enrollment from triggers; manual enrollment is unaffected.
đ Note: This mirrors how repeatable triggers already work in Workflows, so the enrollment rules will feel familiar if you have configured repeatable workflow triggers.
You can now let a single job respond every time a contact repeats an action, so a student who submits a second inquiry, resubmits a form, or has a new alert or case created gets the same automated follow-through instead of being permanently skipped after their first enrollment. Teams that need a job to run only once keep that behavior by default.
