Getting many log entries about outgoing messages that need to be (re-)sent for messages that have already been handled by saga

[Xiard]

I am using Rebus 8.4.4 on AWS (hashicorp 5.100.0). We are using PostgreSql 16.9 as the back end running in AWS. The server is ASP.NET deployed to an EC2 instance.

Note that I am NOT an AWS or Rebus expert; our code was written by an employee that left the company, and I'm trying to stumble my way through it.

We are seeing two issues that may be related:

• ELB health checks are failing constantly; the server is restarting multiple times per hour, making the server unusable
• We are getting extremely frequent Rebus log messages

Example sequence of messages:

2025-07-28T13:52:41.8427840Z: Found 1 outgoing messages to be (re-)sent... will do that now
2025-07-28T13:52:42.7847013Z: Message with ID "0efcb975-7eed-4e48-b068-b0d590c1cc12" has already been handled by saga with ID 385b8acd-a7e8-4cd5-812f-ef69c3fcd5af
2025-07-28T13:52:42.7861696Z: Found 1 outgoing messages to be (re-)sent... will do that now
2025-07-28T13:52:43.1437318Z: Message with ID "0efcb975-7eed-4e48-b068-b0d590c1cc12" has already been handled by saga with ID 385b8acd-a7e8-4cd5-812f-ef69c3fcd5af

The messages are constant. It smells to me like something is getting messed up in the database and I need to somehow clear these messages out so they will stop attempting to re-send.

FWIW, we do setup deferred messages to do automatic polling:

await _bus.DeferLocal(TimeSpan.FromSeconds(30), new LotcJobPollCommand { EntityId = message.EntityId });

Any thoughts? Right now I'm at a loss, and it seems like we have to find some way to make these log messages stop. Perhaps this is normal Rebus operation; I don't know. But having these messages appear multiple times per second in the log seems like it can't be right.