AutomaApp
Schedule in a "specifc date" doesnt start at the sharp time
Describe the bug when I set several workflows (three or four) to start at 00:00:05 "on a specific date", usually starts at 00:01:05 (with a minute or more of delay) for almost the all workflows, sometime just one start on time and the rest start with delay. I tried to set every workflows with 10 seconds of gap between each other and start 1 minute of delay as well
In the last two weeks, some days happen that neither of the workflows start at all.
There is a bug? Is impossible to fix the schedule in order to starts sharp (in the seconds set before)
To Reproduce Steps to reproduce the behavior:
- Go to 'Schedule', select a few workflows, add trigger on a specific date,
- Select a specific date, and set the time in 00:00:04, 00:00:14; 00:00:24. (try near midnight)
- See error
Expected behavior workflows should start always sharp at the time.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: Windows 10 Enterprise and I tried in Mac OS
- Browser: Google Chrome
- Extension Version: 127.0.6533.122 (Build oficial) (64 bits)
Additional context Add any other context about the problem here.
Automa uses browser.alarms (see here) to create alarms. However, on Chrome, unless the extension is loaded unpackaged, the alarms it creates are not allowed to fire more than once per minute (see details here).
A couple of alternatives that might be worth trying:
- Use Firefox instead of Chrome
- Avoid scheduling more than one script per minute
