HangfireIO / HangfireIO/Hangfire
Wrong next execution time
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
Hi,
I'm using Hangfire 1.8.5 with SQL Server, .Net 7.0 and running on Azure App Service.
A recurring job is set to be triggered every 3 hours, but the next execution is with a wrong value.
Is that a bug?
Or maybe something set wrong?
Contributor guide
Research direction
The report mentions Hangfire 1.8.5 with SQL Server, .NET 7.0, and Azure App Service, but names no source files, tests, or entry points. Start by comparing the configured three-hour recurring schedule with the displayed next execution time and checking the relevant schedule and time-zone settings; done means determining whether the value is expected or reproducibly wrong.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, sql
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100