Accurate trigger behavior when testing automations with weekly frequency

andy_burt

The "Test now…" feature currently doesn't reliably reflect what will actually happen when an automation is triggered.

I set up an automation using "When a row is changed" as a trigger with a weekly frequency. I wanted to send an update request for only rows where the status had changed to Approved over the last week. When I clicked "Test now…" the update request I received included every row with the status "Approved", not just the one that had changed over the past week. However, when I let the automation run for real this morning, I got a different result. Only the rows I had intended showed up in the update request.

It's great news that my automation works as intended, but running the test should demonstrate what an automation it is actually going to do.