Particular.TimeoutMigration 1.2.2 – Patch release available

Hi everyone,

We’ve just released Particular.TimeoutMigration 1.2.2.

Fixed bugs

  • #265 Timeout expirations are cut in half when migrating to RabbitMQ

How to know if you are affected

You are affected if you used the migration tool to migrate timeout messages into the RabbitMQ transport’s delayed delivery infrastructure.


Migrated timeouts are delayed for half the time they are supposed to be, so they are delivered too soon.

How to handle already migrated timeouts

As long as the cleanup procedure for timeout manager data has not been performed, it is possible to identify timeouts that have been migrated but not yet delivered. Please contact for assistance with how to ensure these messages are delivered at the correct time.

Should you upgrade immediately

You should upgrade before using the tool to perform more migrations.

Where to get it

You can install the new version from NuGet.

To update an existing global installation, run dotnet tool update --global Particular.TimeoutMigration.

With thanks,
The team in Particular

Please read our release policy for more details.