All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

Run an automation only once per record

The Run each record only once setting stops a record from going through the automation more than once. A failed run doesn’t count, so the record can go through again.

4 min
Before you start · for owners and managers
Permission to edit workflows
  • You need: Permission to edit workflows

Steps

1
Open the automation and press Settings.
2
Turn on Run each record only once.
3
Wait for All changes saved, or press Publish if the automation is on.

Supported triggers

Trigger
Supported?
A new record is added, A field changes, A field stays the same for a while
Yes
Before or after a date
Yes
Another workflow starts it
Yes
A task is completed
Yes, on the linked record
Another app sends data
Yes, only with a unit and matching
On a schedule
No; it runs without a record
Messages and email
No, they have their own rules: Someone messages you for the first time runs once per chat, and email once per email
A record is deleted
No

How it works

The first run that passes the trigger and the conditions reserves the record. Any later run ends as “Skipped — this workflow runs each record only once, and this record already ran.”

The reservation stays for a completed or waiting run. It’s released if the run fails.

The daily check of Before or after a date doesn’t read reserved records again.

Turning the setting off and on again keeps the old reservations. There’s no way to reset them.

The reservation stays even after the run no longer shows in History.

A record moved to another unit keeps its reservation under its old address.

If something goes wrong

What you see
Why
What to do
“Run each record only once isn’t supported”
The trigger is a message, an email, a deletion, or On a schedule.
Turn off the setting.
“Reserved by another run” when you resume
Another run reserved the record.
Don’t resume; the record already ran.

A real example

Namaa Academy
The situation

A client who edits their details gets the welcome message twice.

What they did
  1. A welcome automation on A field changes for the mobile field.
  2. Run each record only once turned on.
The result

Every client gets only one welcome.

A made-up company, to show the idea. The numbers are rounded.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.