Scheduled job tries to 'catch up'
See original GitHub issueUsing code
schedule.scheduleJob("*/5 * * * *", function(){ doStuff(); });
Whenever the device is powered on, and this app starts automatically on startup, it looks like it runs through and executes all the missed times. For example, the above runs every 5 minutes normally, but if the device is powered off for an hour and plugged back in, it executes 12 times in quick succession before resuming normal functionality.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:9
- Comments:14
Top Results From Across the Web
Why Scheduling Catch Up Days for Next Year Could Save ...
A catch up day is simply a day when you can catch up on tasks you've pushed aside and nothing else is scheduled....
Read more >about Scheduled Jobs Troubleshooting - PowerShell
When a scheduled job runs, it creates an instance of the scheduled job. To view, manage, and get the results of scheduled job...
Read more >How to Catch Up on Work When You're Behind [Pro Tips!]
How to Catch Up on Work When You're Behind [Pro Tips!] · Prioritise Your Tasks. When you figure out which tasks need to...
Read more >Problems with Get-ScheduledJob and Try Catch Finally
function ViewOnly { try { $try = Get-ScheduledJob -ErrorAction Stop } catch { $ErrorLine = $_.InvocationInfo.Line $ErrorMessage = $_.
Read more >How to Catch Up on Work When You're Behind - Calendar App
Compared to trying to push through when stuck, research shows that switching to another unrelated task improves performance. So, the next time ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Noticed this, too. Happens on a Windows 10 machine after waking up from hibernation. This is pretty uncool as the job contains a call to a rate-limited API.
Confirmed this behavior running on a mac. The system was put to sleep and when it came back online the jobs all ran to catch up.