Hi @OAJ! 

Welcome to the Airtable community!

One reason why your tests may be working, but this automation does not work in practice might have to do with the fact that the automation is running prematurely. This has to do with how/when Airtable recognizes a record as being updated. Airtable updates the "last updated" time of record to be as soon as a change is initiated, not after you have left the cell, this means you could be partly through changing a name when Airtable decides to trigger your automation and essentially there is not enough time for Airtable to know your new values, causing errors in your automation flow.

The way most people get around this is by using a different trigger that waits some period of time before your automation runs, giving the user enough time to input their changes before the automation runs. They employ a formula field that compares the NOW( ) function to the "Last Modified Time" field in Airtable:
"IF({Last Modified} < NOW(), "run automation")" essentially this field would be blank immediately after a change, and then eventually would read "Run Automation" once the NOW( ) function updates. The downside is that the now( ) function is not consistent in Airtable, it updates range from 1 minute - 10 minutes at times but is typically updated every 5 minutes, which means there could be some delay between changes.

You would change the trigger of your automation to "When conditions are met" and check for "run automation" in your formula.

 

I would also double check that you are referencing the correct RecordID in your loop/update record step, just incase. 

I hope this helps! Please let me know if you have questions. 

- Chantal 

 

Hi @OAJ! 

Welcome to the Airtable community!

One reason why your tests may be working, but this automation does not work in practice might have to do with the fact that the automation is running prematurely. This has to do with how/when Airtable recognizes a record as being updated. Airtable updates the "last updated" time of record to be as soon as a change is initiated, not after you have left the cell, this means you could be partly through changing a name when Airtable decides to trigger your automation and essentially there is not enough time for Airtable to know your new values, causing errors in your automation flow.

The way most people get around this is by using a different trigger that waits some period of time before your automation runs, giving the user enough time to input their changes before the automation runs. They employ a formula field that compares the NOW( ) function to the "Last Modified Time" field in Airtable:
"IF({Last Modified} < NOW(), "run automation")" essentially this field would be blank immediately after a change, and then eventually would read "Run Automation" once the NOW( ) function updates. The downside is that the now( ) function is not consistent in Airtable, it updates range from 1 minute - 10 minutes at times but is typically updated every 5 minutes, which means there could be some delay between changes.

You would change the trigger of your automation to "When conditions are met" and check for "run automation" in your formula.

 

I would also double check that you are referencing the correct RecordID in your loop/update record step, just incase. 

I hope this helps! Please let me know if you have questions. 

- Chantal 

 

@AirOps 

Thanks for the response!

I tested out your theory by copy and pasting a new value rather than typing it which would eliminate the initiation timing if I'm not mistaken, but still no changes to the records on the other table. I suspect it has something to do with the RecordID as thats usually the problem with my automations. I forgot to mention that I have the "Update Record" set up as a repeating action.

The "Find Records" step I have the table set to "Pre-Approval," which is the table that I want to automatically update based on the first. I have the "Find Records based on" set to "View" and "View" set to "Grid View."

The Record ID of the "Update Record" step I have set to "Airtable record ID"