We’ve just released Particular.TimeoutMigration 1.2.2.
- #265 Timeout expirations are cut in half when migrating to RabbitMQ
Migrated timeouts are delayed for half the time they are supposed to be, so they are delivered too soon.
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
firstname.lastname@example.org for assistance with how to ensure these messages are delivered at the correct time.
You should upgrade before using the tool to perform more migrations.
You can install the new version from NuGet.
To update an existing global installation, run
dotnet tool update --global Particular.TimeoutMigration.
The team in Particular
Please read our release policy for more details.