Skip to main content

Automation Settings

Most of an automation can be changed after it's created — the schedule, the recipients, the name. Three things freeze permanently the first time it fires.

Opening automation settings​

Open the automation from the Automations page. Its detail view has three tabs — Overview, History, and Rows for batch automations — and editing is done from there.

Separately, Automation Settings is a workspace-wide screen, available to Owners, holding two defaults that apply to every automation: how long batch rows are kept, and how many consecutive failures pause an automation (5 by default).

You can't half-apply an edit

Flowera refuses an edit while a fire or batch of that automation is running — you get a conflict error rather than a run that used half the old configuration and half the new one. Wait for the fire to finish, or pause first.

Renaming and describing​

The name is what you'll see in the list, in notifications, and in a fire history six months from now. Say what it does and to whom: Daily lead digest — sales channel rather than Automation 3.

Renaming is safe. Nothing references an automation by name.

Changing what it runs​

You can change the schedule or time zone, and edit the row mapping and data source of a batch.

Three things can't be changed once it has fired

The flow it runs, single vs batch mode, and the trigger type are fixed from the first fire onwards. Until then — while it's still a draft — all three are editable.

Submitting a change to one of these after the first fire returns success and silently does nothing. Re-read the automation after saving if you're not sure, and create a new automation when you need to point at a different flow.

Changing a batch's data source deserves care: new columns mean the row mapping needs revisiting. Preview the rows before saving.

Deleting the flow deletes the automation — along with its whole fire history, immediately and without a warning. It isn't paused and there is nothing to restore. Delete the automation first if you want to retire a flow deliberately.

Enabling and disabling​

Pause stops future fires; a fire already running finishes. Resume re-arms it, and the next fire is the next scheduled occurrence — it does not catch up on what it missed while paused.

That last part matters for daily jobs. A digest paused for three days doesn't send three digests on resume; it sends tomorrow's.

Firing manually​

Fire Now runs the automation immediately, exactly as a scheduled fire would.

For a recurring automation it runs once and leaves the schedule alone. For a one-shot it consumes the schedule — it has fired, so it won't fire again at its appointed time.

Deleting an automation​

Deleting is permanent and takes the fire history with it. Only the workspace owner or the person who created the automation can do it.

If you might want it back, pause it. A paused automation costs nothing.

Deleting an automation doesn't touch the flow it ran, the executions it produced, or the messages it sent — those are all still there.