Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Long running Scheduled Tasks mean ones later in the list may not run #49

Closed
bn-jdcook opened this issue Jan 18, 2024 · 1 comment · Fixed by #51
Closed

Long running Scheduled Tasks mean ones later in the list may not run #49

bn-jdcook opened this issue Jan 18, 2024 · 1 comment · Fixed by #51

Comments

@bn-jdcook
Copy link

If you have multiple ScheduledTasks that are scheduled for the same time and the first one takes more than 60 seconds the second one is not ran. It appears to be because "now" is computed at the time each Task would run rather than at the beginning of the run.

bn-jdcook added a commit to bn-jdcook/TaskSchedulerBundle that referenced this issue Jan 19, 2024
NicoHaase added a commit that referenced this issue Jan 23, 2024
NicoHaase added a commit that referenced this issue Jan 23, 2024
NicoHaase added a commit that referenced this issue Jan 23, 2024
NicoHaase added a commit that referenced this issue Jan 23, 2024
@NicoHaase
Copy link
Collaborator

Can you check whether #51 resolves the problem?

NicoHaase added a commit that referenced this issue Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants