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
It seems that when calling ReceiveMessage on a queue, the VisibilityTimeout provided in the request is not used and is not set on received messages. Instead the VisibilityTimeout defined on the queue (defaults to 30 seconds without config) is provided by default. You can see this happening here.
It looks like it IS possible to change the message visibility using the ChangeMessageVisibility operation.
I believe this is an important functionality that should be supported here to adhere to the SQS API specification and provide a valid testing interface.
The text was updated successfully, but these errors were encountered:
It seems that when calling
ReceiveMessage
on a queue, theVisibilityTimeout
provided in the request is not used and is not set on received messages. Instead theVisibilityTimeout
defined on the queue (defaults to 30 seconds without config) is provided by default. You can see this happening here.It looks like it IS possible to change the message visibility using the
ChangeMessageVisibility
operation.I believe this is an important functionality that should be supported here to adhere to the SQS API specification and provide a valid testing interface.
The text was updated successfully, but these errors were encountered: