Skip to main content
Question

Automation Runs More Than Once

  • Oct 3, 2026 7:36 PM UTC
  • 9 replies
  • 176 views

Forum|alt.badge.img+3

I’m having an issue with an Airtable automation where the same record occasionally triggers the automation multiple times even though I only expect one run per change. This results in duplicate actions being performed and makes it difficult to keep the workflow consistent.

  • The trigger is based on a record being updated.
  • Some records cause the automation to run twice unexpectedly.
  • The duplicate runs happen intermittently rather than every time.
  • There are no intentional loops or duplicate automation steps in the setup.

Has anyone dealt with duplicate automation runs like this? What should I check in the trigger configuration or record-update logic to prevent the same change from being processed more than once?

9 replies

ScottWorld
Forum|alt.badge.img+35
  • Genius
  • Oct 4, 2026 4:30 AM UTC

The only way that you can reliably use the trigger for “record being updated” is if you’re using a single-select field, a checkbox field, or if the record is being updated through the API (such as updating a record with a Fillout form).

Otherwise; every time you type a keystroke; it counts as the record being updated. If you make several keystrokes in quick succession, it might be bundled together as one update. But that’s the crux of the problem.

I would recommend changing the trigger to “when a record matches conditions”.

Or, if you want to stick with “when a record is updated”, I would use a single-select field because you can also use the single-select field to deliver messages to the user as the automation is running  I explain this concept more in this thread.

Hope this helps!

If you have a budget and you’d like to hire the best Airtable consultant to help you with this or anything else that is Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld


jills
Forum|alt.badge.img+9
  • Inspiring
  • Oct 4, 2026 2:09 PM UTC

As ​@ScottWorld said, you could use “When record matches conditions”...

In some cases, I have “Trigger” fields that are Formula fields (formatted as single select). This trigger field can be based on things like Last Modified Time, but you can also set it to run 5 (or longer) minutes after the last modified time in case multiple fields are being updated. You can wrap up a lot into that formula field to help you trigger when to run the automation.


TheTimeSavingCo
Forum|alt.badge.img+32

Hm could you provide a screenshot of the automation trigger setup and talk a bit about how the field(s) that trigger it have their data filled in?

If you could provide screenshots of the revision history of affected records that’d be interesting too and  might let us see exactly what happened (revision history sometimes gets compressed though if stuff happened too quickly)


Forum|alt.badge.img+7
  • New Participant
  • Oct 5, 2026 11:56 PM UTC

One thing I’d check is whether the first automation run is indirectly causing another update to the same record. For example, if a later step changes a field on the triggering record, that can create another qualifying update even though there isn’t an obvious loop in the automation. I’d also check whether other automations, scripts, or integrations are writing to that record around the same time. Does the duplicate run happen after the automation makes an update, or can it happen even when nothing else touches the record?


Alexey_Gusev
Forum|alt.badge.img+25

Hi,
You should review history.
If you update text field by typing new value, probably it runs in the middle of typing, as ​@ScottWorld said. You should update by pasting the whole value or use other field type with “instant” change like single-select etc. Example - I’m trying to type “Test” in “Notes” field in the similar case.

 

 


phoebelindo
Forum|alt.badge.img+10
  • Participating Frequently
  • Oct 6, 2026 3:59 PM UTC

If you need the automation to be driven by a text field, another approach is to separate data entry from the trigger itself. Have users enter their text normally, then click a button in an Interface to submit it. The button can update a dedicated status field (checkbox or single select), and the automation can trigger from that field change instead of the text field. This avoids multiple runs caused by users actively typing and gives you more control over when the automation actually starts. Then you’d just have to make sure the automation resets the trigger field at the end so it can be reused.


Forum|alt.badge.img
  • Participating Frequently
  • Oct 7, 2026 2:00 PM UTC

Depending on what needs updating or how quickly you need data updated, you could also try the “When a record enters a view” trigger or the “At a scheduled time” trigger.

“When a record enters a view” is great if you want to set a specific set of conditions for it to trigger and, if needed, also include conditions once the record has been updated to filter it out of the view so it won’t trigger again.

“At a scheduled” time works great if you need to run a batch of record updates at specific times; the only downside is it may not be instant.


Kitkate
Forum|alt.badge.img
  • New Participant
  • Oct 30, 2026 3:48 PM UTC

I dealt with this in different ways depending by the need.
All the suggestions above are very valid, so I will only add a couple more if none of the above meets your need. :) 

Option 1 - Narrow down the fields where an update would trigger the automation
If only some fields are relevant, in the Trigger Details I would specify the fields the automation has to monitor for updates.


Option 2 - Add a "delaying field"
Create a field "Last modified time" and add it to your view/table.
Create a formula field "Ready for automations?" (I'm very literal when I give a name to the fields in my tables :D)
Let's say want to add a delay of 5 minutes to the trigger. The formula is very basic, it should be like this:
DATETIME_DIFF(NOW(), {Last modified time}, 'minutes') >= 5
It calculates the time difference between the current time and the timestamp of the last modified time, in minutes (you can do it in seconds, etc.). When the 5 minutes have passed, the field value will be "1" (instead of 0). 
In your automation, add to the conditions  "Ready for automations?" = 1.
This will guarantee that the record is back to a "stable" condition after being updated, and it's safe to trigger the automation. 

This is my "go to" option when I need to capture any updates, but at the same time I'm conscious that users may type, delete, type again, update different fields etc. and I want the automation to run only at the very end, when the record has been finalised.  


Luc_00
Forum|alt.badge.img+1
  • New Participant
  • Nov 2, 2026 9:37 PM UTC

The trigger fixes above cover the cause well (@Kitkate's delay field is the one I'd try first). One thing I'd add: make the action itself safe to run twice, because occasional double runs are hard to rule out completely.

- If the automation creates records: start with a "Find records" step that looks for a record created from the same source (store the triggering record's ID in a field for this), and put the "Create record" step in a conditional group that only runs when nothing was found.
- If it sends an email or calls a webhook: in the same run, write the date into a "Sent at" field on the triggering record, and add a condition at the start so the automation only continues when "Sent at" is empty.

Neither catches two runs in the very same second, but they stop the typical case.

For duplicates you already have: group a view by that source field and sort by created time; any group with more than one record holds a duplicate. Take a manual snapshot before deleting them, just in case.