Is Pipes not respecting Standard SQS delays on specific messages?

Question

I have recently implemented a feature so that Pipes acts as a consumer to a Standard SQS queue sending the messages over to a Step Function. Part of my implementation however was to add varying delays per message sent to the SQS queue, I imagined that the Pipe wouldn't be able to pick up the message and send int over to the Step Function until the delay was over.

But it all seems pretty immediate. So maybe I mean in my question - is this expected behavior? Can you reproduce what I am describing?

Answer

Pipes use the same mechanism to read messages from the queue as any other client, so it doesn't make sense.

Note that you can specify a delay configuration on the queue, but also on the SendMessage API call itself (which overwrites the queue definition). Also note that the value is in seconds.

My guess is that you have something wrong in your API calls.

Is Pipes not respecting Standard SQS delays on specific messages?

Contenus pertinents