Skip to main content

Hey everyone,


I’m having an issue with a conditional automation. Everything appears to be triggering and working correctly when things happen slowly. However, I made a script that is meant to set the conditions for another trigger. It seems like this is happening too quickly, and the automation is only triggering once instead of a few times.



The script affects the K1 Override? field. My organization has to run a random lottery for our kindergarten class, and that is what the script is doing. Whoever is selected, it writes in “Selected”,

otherwise “Not Selected”.The Status field has a formula that notices this and updates accordingly. The automation is triggered by the Status field.



Here’s a screenshot of the trigger’s criteria:



And one of the individual conditional actions:



Has anyone experience this? Where an automation gets overloaded or something?



  • Mike

Yes, AT automations have a poll time built in. Even when they say “instant”, I’ve found it can be up to 2 minutes. If you can script in a wait to prevent super-rapid changes, that would be your best bet to get this one working.

Yes, AT automations have a poll time built in. Even when they say “instant”, I’ve found it can be up to 2 minutes. If you can script in a wait to prevent super-rapid changes, that would be your best bet to get this one working.


Hi Alyssa,


Thanks so much for your help! I tried this out, and was able to make a delay with the following:


function timeout(ms) {

  return new Promise(resolve => setTimeout(resolve, ms));

}



async function test(ms) {

    await timeout(ms);

}



await test(300);

This still didn’t seem to be working. So I tinkered with the trigger conditions. Instead of having multiple criteria (with OR), I tried just “when record is updated”, focusing on that field. By simplifying this, it seems like Airtable can more easily handle the rapid triggers, and it worked!


Thanks for your support. I hope someone else can benefit from this.

Reply


Terms & Conditions