kombu

kombu copied to clipboard

It's my understanding that defining a visibility timeout is only applied during SQS queue creation. This is described in https://github.com/celery/celery/pull/7234

As a user, it is unexpected behavior that once a queue exists, whatever value you set for a visibility timeout is silently ignored.

The receive_message method on the SQS client supports a VisibilityTimeout argument that can be used to override whatever was set as the default for the queue during creation.

It would be nice if this was used so the setting is always respected.

Hey @ipmb :wave:, Thank you for opening an issue. We will get back to you as soon as we can. Also, check out our Open Collective and consider backing us - every little helps!

We also offer priority support for our sponsors. If you require immediate assistance please consider sponsoring us.

@browniebroke