HangfireIO / HangfireIO/Hangfire
Azure slots jobs running old code
Open
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
Anyone have an approach using deployment slots in Azure to only ensure the production instance is running jobs?
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by examining Hangfire's background processing behavior in applications using Azure deployment slots; done would require a clear, validated approach that ensures only the production instance runs jobs without outdated slot code processing them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100