You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature related to a problem? Please describe.
At the time when we wrote the original native delayed delivery implementation it wasn't possible to delay messages really far (or maybe not even possible at all but my memories are blurry). Nowadays a message can be natively deferred with the client up to 7 days. It should be possible to have a similar mechanism like we have in SQS where we deliver messages into the future and redelivery it again for delayed deliveries longer than 7 days.
Describe the feature.
Is your feature related to a problem? Please describe.
At the time when we wrote the original native delayed delivery implementation it wasn't possible to delay messages really far (or maybe not even possible at all but my memories are blurry). Nowadays a message can be natively deferred with the client up to 7 days. It should be possible to have a similar mechanism like we have in SQS where we deliver messages into the future and redelivery it again for delayed deliveries longer than 7 days.
https://learn.microsoft.com/en-us/dotnet/api/azure.storage.queues.queueclient.sendmessageasync?view=azure-dotnet#azure-storage-queues-queueclient-sendmessageasync(system-binarydata-system-nullable((system-timespan))-system-nullable((system-timespan))-system-threading-cancellationtoken)
The tricky part might be that there is no way to deduplicate messages like we can do with FIFO queues
Describe the requested feature
Describe alternatives you've considered
Additional Context
No response
The text was updated successfully, but these errors were encountered: