Azure Event Hubs handler failures retried before checkpointing
When a handler returned RETRY, otherwise failed, or was still handling an event when the sidecar crashed or partition ownership was lost, the event could be checkpointed and never redelivered. Failures now retry with the configured backoff until success or subscription cancellation, and checkpoint progress advances only through contiguous successfully handled events or batches.
Show release-note lines
The Event Hubs pub/sub and input binding components now advance a partition's checkpoint only through contiguous, successfully-handled events or batches: - A handler failure is retried with the configured backoff until it succeeds or the subscription is cancelled, instead of being dropped and checkpointed anyway.github.com/dapr/dapr/releases/tag/v1.17.15