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

Turn on an automation and apply it to existing records

Turning on is a window, not just a button: it shows everything that blocks turning on all at once, then offers to run the automation once on existing records too.

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

Steps

1
Press Turn on in the automation.
2
Review the list in Before you turn it on.
Every problem shows with the step it’s in. Press Fix on each one.
3
Review the warnings.
Turned-off or unconnected steps. They don’t block turning on.
4
Optional: to run it on existing records too, choose Yes, include the … instead of No, only new records.
The number of records that already match shows in the question.
5
Press Turn on.
6
To pause it, press Pause.

The checklist blocks turning on when there’s

A deleted WhatsApp line in a sending step or a trigger, a template that isn’t approved, the tasks unit turned off while there’s a create-task step, a channel not linked to a unit with an action that needs a record, a disconnected mailbox, an invalid schedule, and more. They’re all in Why didn’t my automation run? Every error and its fix.

Which existing records?

The unit’s current records that match the conditions, and that the automation hasn’t run on before, with any result. So turning on a paused automation only reaches the records that arrived while it was paused.

Trigger
Including existing records
A new record is added
Available
A field changes, with a condition
Available
A field changes, without a condition
Not available; it would run on every record
A field stays the same for a while
Not available; records that are due start on their own
A message arrives, An email arrives, On a schedule, Before or after a date and Another workflow starts it
Not available

How does it run?

When the automation sends on WhatsApp, the included records are always spaced out, with gaps between the messages, so the number doesn’t send them all at once. Others run with a 2-second gap between records.

Pausing, publishing a new version, or running out of executions stops including existing records.

Each run shows “included when the workflow was turned on”. A record created after you turn it on is handled by the trigger itself.

Pausing

Pausing stops new runs. Waiting runs end as Skipped when they wake up, unless they reached the goal.

Turning on an automation that has a draft turns on the current version, not the draft.

If something goes wrong

What you see
Why
What to do
“The automation is already on”
You pressed twice.
Nothing to do.
“The automation was changed”
A version was published while the window was open.
Open the window again.
“Including existing records isn’t supported”
The trigger doesn’t support it.
See the table above.
“More records than the limit”
More than 2,000 records.
Narrow the conditions.
“The number changed”
Many records arrived after you opened the window.
Check the new number and confirm.
“Couldn’t start including existing records”
A temporary outage; the automation was turned off.
Try again.

A real example

Shield Security Co.
The situation

A new “Visit every month” automation, and 300 existing contracts with no visits.

What they did
  1. Turned on with existing records included: 300 contracts.
  2. The condition: the status is “Active”.
The result

Visits for the existing contracts were generated within 10 minutes.

A made-up company, to show the idea. The numbers are rounded.

Good to know

Up to 2,000 records can be included. The count reads up to 10,000 records, then shows “2000+”.
If the number grows by more than 20% and more than 10 records over what was shown, you’re asked to confirm again.
A 2-second gap between runs for anything other than WhatsApp.
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.