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

Refactor DefaultTriggerScheduler and handle past StartAt triggers #5463

Merged
merged 1 commit into from
May 29, 2024

Conversation

sfmskywalker
Copy link
Member

@sfmskywalker sfmskywalker commented May 28, 2024

The DefaultTriggerScheduler received a significant refactoring, with the injection of the ISystemClock service and a modification of several method calls. Additionally, a check is included to avoid scheduling StartAt triggers if their execution time is in the past. For these triggers, an information message is logged and scheduling is skipped.

Fixes #5454


This change is Reviewable

The `DefaultTriggerScheduler` received a significant refactoring, with the injection of the `ISystemClock` service and a modification of several method calls. Additionally, a check is included to avoid scheduling `StartAt` triggers if their execution time is in the past. For these triggers, an information message is logged and scheduling is skipped.
@sfmskywalker sfmskywalker requested review from a team May 28, 2024 21:06
@sfmskywalker sfmskywalker merged commit 411151d into main May 29, 2024
7 checks passed
@sfmskywalker sfmskywalker deleted the bug/5454 branch May 29, 2024 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

StartAt activity re fires on server restart
2 participants