Repository navigation
UseDurableOutboxOnAllSendingEndpoints not working for EF Core #2599
Description
Describe the bug
Outbox for EF Core does not work as expected. I tried but couldn't find the reason.
UseDurableOutboxOnAllSendingEndpoints does not save any data in wolverine_outgoing_envelopes table.
dotnet run -- describe shows that the message is durable.
but it does not take part in the outbox (note only Task item is shown as saved in the log).
If the RabbitMQ is stopped the message is discarded.
To Reproduce
Steps to reproduce the behavior:
- Clone WolverineOutboxTest repo
- From Root directory run docker-compose.yml to start RabbitMQ and PostgreSQL and dotnet ef database update to apply migrations
- After running use swagger to post data
- Check
wolverine_outgoing_envelopestable. The message sits there (indefinitely?).
Expected behavior
EFCore + Outbox should work with UseDurableOutboxOnAllSendingEndpoints.
Activity
BlackChepo commentedon Apr 27, 2026
Looks like a duplicate of #2588, fixed on main in 113628d (PR #2596) on 2026-04-26 — three days after 5.32.1 was released, which explains why you're still seeing it.
Your config (EF Core + Postgres + RabbitMQ + UseConventionalRouting() + UseDurableOutboxOnAllSendingEndpoints() + a registered handler) matches the failing scenario exactly.
Root cause: when a handler is registered, conventional routing pre-compiles the sender exchange before DiscoverSenders runs, so the AllSenders policy short-circuits on
e.Subscriptions.Any() and the endpoint stays BufferedInMemory. describe shows the route but not the actual mode, which is why it looks durable but isn't.
Regression test for your exact setup: Bug_2588_ef_core_durable_outbox_with_conventional_routing.cs.
jeremydmiller commentedon Apr 27, 2026
This did turn out to be a duplicate. Fix coming in just a couple hours