Orchestrator queue fills up but there are no messages on it
Open
- Dominant language
- C#
- Stars
- 1.7k
- Forks
- 335
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 6
Description
We have several environments running durable task orchestrations and in each environment, this behavior is the same. Our orchestrator queue fills up after a few months and all orchestrations then fail. There are no messages on the queue. I'm reaching out to Microsoft support in case this is an Azure issue, but this only happens with our use of the durable task framework, so I'm posting here as well.
Are there any settings I can pass in when creating the task hub worker or client that can address this?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.