Azure / Azure/azure-functions-durable-js
Durable timer more than 6 days in the future can not be created
- Dominant language
- TypeScript
- Stars
- 142
- Forks
- 66
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 4
Description
**Describe the bug**
When I create a durable timer in an orchestrator function with a date larger than `now + 6 days`, the timer is not started. There is no error. Apparently there used to be a limitation in this SDK which did not allow timers 7 days in the future.
**To Reproduce**
See [repro](https://github.com/sladkoff/durable-timer-repro) for more detailed information and manual reproduction steps.
**Expected behavior**
A timer is started and added to the orchestration history.
**Actual behavior**
A timer is not started and not added to the orchestration history.
**Additional context**
Related [issue](https://github.com/MicrosoftDocs/azure-docs/issues/95643).
Contributor guide
Research direction
Start with the linked durable-timer-repro and reproduce the difference between timers six and seven days in the future. Trace the durable timer scheduling entry point and orchestration history behavior; done means a timer beyond six days starts and appears in the orchestration history without an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100