Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Recurring task starting at fixed delays
See original GitHub issueOne can, at the moment, create a RecurringTask that gets rescheduled with FixedDelay, but it is indeed a fixed delay between a previous completion of the task and new scheduled completion.
That means that if a task is a recurring task with FixedDelay of 5 seconds, and the task is scheduled for 14:00:00.00, actually starts at 14:00:00.05 and takes 0.3 s to execute, the next execution will get scheduled for execution after 14:00:05.08.
Is there a way to achieve recurring task that will get scheduled for 14:00:00.00, then 14:00:05.00, then 14:00:10.00 etc., without a time drift caused by execution time and a delay between planned execution time and actual picking of the task?
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I have exposed the
Executionin theExecutionContextin master now. See commit c3528353dd12b5e8c2be8d5d7d1b229b70eb4a30I know this thread is old, but we recently fixed a bug which limited the throughput of the scheduler if that is of interest.