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

currently SQL tool is only allowed with stored procedure and functions, 

can we extend it with writing queries 

In Explorer, Add a new folder and give it a name: ABCD.

Open Settings > Security

Press Resouces ...

Observe newly created folder is named New Folder and not ABCD

I am not able to write test cases for a few workflows because Warewolf test framework is crashing. After a detailed investigation, we found that if we used any tools from the list below in the workflow, the Warewolf test framework would not respond.

• Sequence
• For each
• Select & Apply

We faced similar problems in different warewolf version. We tested in latest 2.8.7.1 version as well in previous 2.8.2.9 version.

Test framework error :

cryptocurrency exchange script

Thanks....

Docker container is not able to connect to remote server for Unit Test, currently we are pulling warewolf version 2.8.6.16

Hello team,

Is it currently possible to connect to Polybase using the existing Warewolf functionality or, would a tool need to be created?

Regards,

Wynand

Hello , 

Warewolf Server Configuration 

Warewolf version - 2.8.1.3

Workflow - 1200 

CPU(s) - 16 cores 

RAM - 64 GB 

we are deploying Warewolf server using azure pipeline. the command we are using to refresh workflow is 

powershell -ExecutionPolicy Bypass -Command "Invoke-WebRequest http://localhost:3142/services/FetchExplorerItemsService.json?ReloadResourceCatalogue=true -UseBasicParsing -UseDefaultCredentials"

as you can see in above screenshot , it is hang up there by 1 hours , in most case it should be finish by 10 secs. 

could you please support us to fix this problem ? 

anyone tell me?

We have identified that if we are not using actual values for DB and other resources for workflows it fails Unit tests.

It causes issue while unit test run when unit test container connects to actual DB and other resources, there might be chances of Data manipulation at Unit test level.