I can’t seem to find a specific answer to this question: How do I immediately release and/or bypass a delay after queue event for the first event in the queue.
I have a Zap that I want to run immediately upon the trigger. However, the trigger may be invoked by users multiple times (usually, by accident). To solve this, I’ve implemented a 5 minute delay after queue and some filtering logic to prevent errors and other odd behavior if the Zap is triggered multiple.
It seems that even that first item is delaying for 5 minutes. I don’t want that. I just want subsequent items in the queue to be delayed.
The exact behavior of the first item doesn’t appear to be documented, although the docs seem to hint that every queue item will be subject to the delay.
If that’s the case, I’d like to propose a feature request to delay after queue for a simple yes/no toggle that would allow the user to decide if the delay should be applied to the first item or not.
The workaround, in my head, is some weird combination of a storage and code script that determines whether or not the zap has recently run, and changes output based upon that to edit the “delay” feature.
