Regression in Post Tool Mapping – Warewolf v2.8.6.16 vs v2.8.1.3

Hi Warewolf Team,

We've encountered a regression issue with the Post tool in version 2.8.6.16. Specifically, the tool fails to map data correctly when posting to RabbitMQ. After some investigation, we confirmed that downgrading to version 2.8.1.3 resolves the issue — the mappings function as expected in that version.

This tool is central to several of our microservices workflows, particularly those under the Tech Titans initiative, so the impact is significant.

Steps to reproduce:

1. Use the Post tool in v2.8.6.16 to send data to RabbitMQ.
2. Attempt to map the data.
3. Observe that mapping fails or data is not passed as expected.
4. Roll back to v2.8.1.3 and observe that the same mapping succeeds.

Additional notes:

• There are a number of prior posts in the community related to the Post tool not working as expected.
• This issue appears to have resurfaced or persisted in the latest versions.
• We'd appreciate clarity on whether a fix is planned or if a stable workaround exists.

The following snips indicates how it maps correctly in v2.8.1.3:

The following snips indicates how it incorrectly maps in v2.8.6.16:

Additional steps taken:

I also took the workflow that works in v2.8.1.3 and then ran it in v2.8.6.16 and got the following result: (Please note it works in v2.8.1.3)

I do have a sample workflow that I can provide, but not on the community, as it will expose the authorization token used by the client. Please contact me for this, and I will provide it to you.

Thanks in advance,

Wynand