Add "Seconds to the "Delay" module

Shlomo Z

Member
Today I had a huge Automation:
Trigger --> Google Sheets to ---> Google Drive --> Mark As Shared --> Save as PDF to DropBox.
The Automation was supposed to trigger a new row every 1-second.
There were approximately 100 Rows per sheet & 9 Sheets (Total 900 Triggers/Automations).

The problem was that it seems like the Trigger was happening too quickly from one row to the other & many rows were "missed" (The PDF never showed up in my Dropbox).
The only way it worked without "skipping" rows was when the trigger was delayed for approximately 7 seconds between each other (we waited 7 seconds between each trigger).

This could have been solved if I added a delay step of 7 or 10 seconds "Delay" on the last step of my workflow.

However, Pabbly does not allow a delay in seconds, we must use "minutes".
A 1-minute delay is too long between each trigger.

Please add "seconds" to the delay module to avoid issues like this in the future.
 

Neeraj

Administrator
Staff member
Cron has a minimum possible resolution of 1 minute and it is a default utility of the Unix systems and is very very stable.

There are other ways to do it but they are not 100% accurate.

So implementing them will create more problems like:

Why my delay didn't execute in exact 10 seconds. Instead, it triggered in 25 seconds.
 

Attachments

  • 250708148_10226236036348215_843848681881325571_n.jpg
    250708148_10226236036348215_843848681881325571_n.jpg
    29.3 KB · Views: 190
Last edited:
Top