[Bug] AzureStorage queue can become stuck on corrupt message.
- Dominant language
- C#
- Stars
- 1.7k
- Forks
- 335
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 6
Description
**Issue**
DurableTask.AzureStorage does not have a dead-letter equivalent like ServiceBus does. This means that a corrupt message in the queue can effectively block a worker permanently, until that message is manually removed. If you somehow get a message in a control queue which DTFx.AzureStorage can not deserialize without throwing, the worker will get stuck on that message. Repeatedly de-queueing it and throwing, never progressing onto the next message in the queue. In ServiceBus this is handled by eventually dead-lettering that message, removing it from the queue after so many failed deliveries.
**Request**
Implement a dead-letter equivalent to ServiceBus, where if the same message fails to be processed some number of times. Ideally there would be some way to store and flag the failed message for review later on.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.