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

Cron trigger outside range firing anyway? #2307

Open
bencyoung-Fignum opened this issue Mar 25, 2024 · 1 comment
Open

Cron trigger outside range firing anyway? #2307

bencyoung-Fignum opened this issue Mar 25, 2024 · 1 comment

Comments

@bencyoung-Fignum
Copy link
Contributor

Describe the bug

Not sure if this is a bug or intended. We're setting a cron trigger with a start and end date where both are already expired (we'll fix this anyway but just want to check the desired internal behaviour). E.g.

With start date = 01-01-1970
End date = 01-01-2023
Cron = "0 30 14 ? * MON,TUE,WED,THU,FRI *"

                return builder
                    .StartAt(startDate)
                    .EndAt(endDate)
                    .WithCronSchedule(cron, m => m.WithMisfireHandlingInstructionFireAndProceed());

Expected behaviour is the trigger never fires, but the actual behaviour is it schedules for 01/01/1970 14:30:00 +00:00, which then runs immediately due to misfire handling I think

Version used

3.8.1

To Reproduce

The steps above.

Expected behavior

The trigger never fires.

@jafin
Copy link
Contributor

jafin commented Mar 25, 2024

Related #1545

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

No branches or pull requests

2 participants