Looking for a workaround to send SQS message from a Sub Workflow

Help me Build my Workflow
,
1

I reported the core bug here: AWS SQS node only sends 1 message for two executions triggered in parallel · Issue #20168 · n8n-io/n8n · GitHub

I’m wondering if anyone has a workaround for this?

I have a workflow that triggers a subworkflow for each input item. I can see multiple new executions in the history for the sub-workflow, so I know that part is working. Where it fails is that the SQS node (in the child) only sends one message for both executions. And the execution history shows the same “Message ID” in the SQS node’s output.

Simple workflows that demonstrate and reproduce the bug are included in the GitHub issue link above.

Any ideas?

2

This is resolved.

Thanks to Vishal for pointing out the solution. I mistakenly believed that the Deduplication Id was tested with a Message Group. So, as long as Message Groups were unique, dedupe ID would not matter. Changing the dedupe id, seems to resolve the issue.