Documentation: How are failure scenarios handled for distributed publishers/subscribers?

[zejji]

I am interested in using MessagePipe both as an internal message dispatcher (like Mediatr) using the in-memory provider, as well as for fire-and-forget asynchronous background jobs (like Hangfire, CAP or Quartz.NET) using the Redis provider.

However, I've reviewed the README.md file in full and couldn't see any detailed mention of what happens in failure scenarios in the latter case.

Specifically:

• what happens when a message triggering a background job is published async via the Redis provider and a subscriber fails to process it, e.g. owing to a bug in the subscriber or a network or other hardware issue?
• is there a concept of retries and/or dead letter queues?
• if so, how is this configured?

[github-actions]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days.