But on the task itself (my second screenshot) it also does not show the queues.
I mean I have no explanation then... The messages have vanished?
I can see the entry in the Cloud Trail too and everything looks fine.
I tried it myself by creating 2 queues and a DLQ. I configured both queues to send unhandled messages to the DLQ. I then sent a few messages to each (using the console Send And receive messages button and I saw the messages in the queue. I Polled for the messages in both queues several times (until the retries were exhausted) and all the messages were sent to the DLQ. I polled for the messages in the DLQ and I saw all messages there. I then started a Redrive task, and selected to redrive to the original queue. All the messages were sent to the their source queue without an issue (was able to verify using the Poll for message).
BTW, the redrive. task shows: source queue/s as this is what you chose. As expected, it doesn't show the queue names (I guess as at the point of starting the task it doesn't know which are the source queues which configured this queue as their DLQ).
- Accepted Answerasked a year ago
- asked 4 months ago
- AWS OFFICIALUpdated a year ago
- Why is my Lambda function retrying valid Amazon SQS messages and placing them in my dead-letter queue?AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 8 months ago
- EXPERTpublished 8 months ago
- A Brief Primer to Onboarding Data To a Healthcare and Life Sciences Data Mesh Leveraging AWS ServicesEXPERTpublished 7 months ago
The second screenshot just shows what you chose when you started the re-drive, i.e., you chose to send to the source queue. You could have chosen to send the messages to some other queue, in that case, you would probably see the queue name there.