(TL;DR "it triggered on all new records, no matter if conditions are met, when they include formula field)
I have following issue:
table1 (near 1500 records) has button field “Confirm match”. when a key pressed, the record partly copied to table2 (by my script, ~500 records), linked to it’s “parent” in table1
table2 contains formula field “Control”, relying on some data including lookup from linked record in table1, result is “OK” or “_error”
“_error” records supposed to be removed, from time to time. I can’t filter at this step, because sometimes “OK” record in table2 may become “_error” after table1 update.
it’s usual process, and it worked as expected.
Now I decided to automate cleanup for table2 and setup new automation “When record matches condition”, second step is Remove record, where Control contains “error” (by way, I was surprised that Remove action is not available, i did that by scripting)
The problem is that trigger works on records, which supposed to be “OK”, while my condition is for “_error”. Automation log shows these records as “_error”.
When i disable automation, and press “Confirm”(my script, creating single record by updateRecordAsync), the record appears in table2 as “OK”
When I enable automation and press “Confirm”, record created for a few seconds (with “OK”), and then removed by automation, supposed it’s “error” record.
My point: that happens because formula calculation has a little millisecond lag, at first it counts as “error” and then “OK”. but during these milliseconds automation got it as target.
I understand many possible workarounds. Maybe i just query record again inside the removal script and check “error” or “OK”, but i think such automation behavior may cause serious issues for someone else.