Hey @EdAirtable ! Don't worry it's not just you, happened to me too when I tried to replicated your situation. Luckily I've got a couple solutions for you that I lay out step by step in this Loom Video.
In essence Airtable is 'too fast' and when you type '50' it registers the 5 first which is less than 35 and triggers the automation (crazy right?)
Essentially you've got 2 choices.
If the data is copy/pasted into the cell from a form or an automation, you're fine, the automation will work as expected (try it).
However if the data is entered manually I recommend you add a new check box field called something like 'Ready To Run?', and add as another condition to your automation that the check box needs to be checked to trigger.
Let me know if that all makes sense !
Yes, it's a well-known issue. Also, if WPM expected to be at least 2-digit, you can add WPM>9 to conditions. But if it can be 100, 110 ... , it won't solve the problem, as it will run with 10 , 11 input data values
Hey @EdAirtable ! Don't worry it's not just you, happened to me too when I tried to replicated your situation. Luckily I've got a couple solutions for you that I lay out step by step in this Loom Video.
In essence Airtable is 'too fast' and when you type '50' it registers the 5 first which is less than 35 and triggers the automation (crazy right?)
Essentially you've got 2 choices.
If the data is copy/pasted into the cell from a form or an automation, you're fine, the automation will work as expected (try it).
However if the data is entered manually I recommend you add a new check box field called something like 'Ready To Run?', and add as another condition to your automation that the check box needs to be checked to trigger.
Let me know if that all makes sense !
Thanks Arthur!!!
The input is from a form, so I'm all clear! Highly appreciate the time you to took help 😉
Love it! Happy to help @EdAirtable . If you found it helpful, can you do me a quick favor and mark my post as the solution? Helps to build my credibility in the community 🙂
