Im getting an error when using the post tool to a server that requires the Accept header:

"The 'Accept header must be modified using the appropriate property or method.
Parameter name: name"

The API setup was working properly before and this error started when I think the API started using the header on their side. Either way, its a coding issue on our end.

This is one Im calling: Investec programable banking, SA PB Account Information : Transfer Multiple v2

Its probably too dificult to setup on your end so happy to help with this where needed.

Hi team,

We recently ran into a number of issues, and upon investigating we've come to the conclusion that the "If there is no error" condition on the Decision Tool doesn't catch all API HTTP errors - the ones we've experienced a number of times is 400, 404, 500, 503, 504.

I have attached a sample workflow, as an example, indicating the standard way we map our API GET or Post tools. Can you please use a similar setup during testing to confirm if all HTTP errors are recognized and caught?

Regards,

Wynand GetCustomerDetails.bite

Service is launched successfully and consumers connected to queues. However, after around an hour or so we would find that the consumers on the journey.welcome.request queue would disappear however the other journey queue were reflecting the consumers fine.

What we found was the queue worker process would die (as per screenshot) the only way to get the consumers back was to restart the warewolf server service

2023-04-21 12:49:07,354 INFO - [00000000-0000-0000-0000-000000000000] - Trigger restarting '05c7daf0-3a79-410e-b101-0c9addf63136'
2023-04-21 12:49:07,573 INFO - [WarewolfLogger.exe] - Logging Server OnError, Error details:Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2023-04-21 12:49:07,573 INFO - [WarewolfLogger.exe] - 4/21/2023 12:49:07 PM [Debug] Error while reading System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
2023-04-21 12:49:07,573 INFO - [WarewolfLogger.exe] - at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
2023-04-21 12:49:07,573 INFO - [WarewolfLogger.exe] - at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
2023-04-21 12:49:07,573 INFO - [WarewolfLogger.exe] - --- End of inner exception stack trace ---
2023-04-21 12:49:07,573 INFO - [WarewolfLogger.exe] - at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
2023-04-21 12:49:07,573 INFO - [WarewolfLogger.exe] - at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
2023-04-21 12:49:07,588 INFO - [Warewolf Info] - queue process died: Journey Start Trigger(05c7daf0-3a79-410e-b101-0c9addf63136)
2023-04-21 12:49:07,729 ERROR - [ at System.Diagnostics.Process.Kill()

What we tried to do was to increase the concurrency to 3 and set the prefetch to 1, and we still experienced the same issue

On deeper investigation it appeared that if the message being process was unable to reach the external api’s for any reason for instance the product api, it would kill the consumers, we tested this by correlating the timelines of when the “product” api was available to when the consumers disappear.

Once we had the “product” api stabilized consumers were stable and remained present

So appears to be a bug with the queue worker when it is unable to process the message correct caused this to crash

My understanding of this is:

• Error was experienced during processing of the message
• That message which is an unack message with the error did not leave RabbitMQ due to the fact that it never received an ack back from warewolf.
• RabbitMQ did not allow additional messages to be processed due to not receiving the ack back (aka message stuck)
• Appear to be the way that warewolf error handling works where it does not send through the ack even if an error was experienced with the message.

Warewolf Logging Settings does not register in ServerSettings.json file when set in the studio.

When splitting a string in WW version it converts value into Date time format as shown below and Datetime is incorrect

Version: 2.8.3.7

"TU015725753-1,1649998986,Savings,470010,A ROUX,2023-05-05,230.000,202305,8,TU015725753-1"

I would kindly like to know if you have in your "ToolBox" along with your Control flow tools, have the ability to open and read the contents of a word document or bonus points a PDF?

Could you kindly point me to one of your example videos demonstrating that? Our customers are dealerships and have a significant amount of paperwork that needs to be automated.

They primarily rely on checkbox inputs on their paper forms.

Dear Team,

For Instance,

[[@productDetails.products([[Index]]).MainPageImage]] 

--> now this Index will be dynamic and will be evaluated in for each loop.

[[Recordset([[Index]]).Name]] --> now this Index will be dynamic and will be evaluated in for each loop.

Hello,

I recently started working on a certain part of the Price Increase Journey that worked last year. What has changed since then? Only the Warewolf version. The workflow in question is the GetPdfLinkDetails which contains an API Post to a 3rd party provider - InsideData. Please note that this API response is an escaped json format. For the sake of completeness, I'm using Warewolf 2.8.1.63.

In the latest version of Warewolf, the API doesn't return a response in Warewolf. Whether the default - output to variable or output to object is selected, as per the below screenshots: 

However, we are able to get a response in Postman as per the following screenshot: 

I then decided to downgrade Warewolf to a version prior to Dev2's Post Tool changes. Once downgraded, upon opening the workflow, I get the following error: 

When I tried to delete the former Post Tool, highlighted in red, in order to drag on a new post tool, I get the following error: 

This concludes the issues experienced. The following is additional information to help with the troubleshooting:

1. The API in question can be called via a post request to the following URL: 
https://generic.insidedata.co.za/ID.Generic.API.TheUnlimited/IDServiceRest.svc/CreateDistributionWithShortener.

The request body is as follow (Please note - should be in Raw Text format - Not JSON:

{
"PassPhrase":"B7CC5331-12A8-46AA-A5B0-D6AB6D4AFC93",
"BusinessID":"TheUnlimited",
"Campaign":"TUG - Price Increase",
"BatchName":"PostMan Test - 2022-08-01",
"DistributionMethod":"SMS",
"DistributionTemplate": "TheUnlimitedInsurance",
"CompositionTemplate":"PriceIncrease",
"TransformData":true,
"Approval":false,
"ArchiveOnly": true,
"LoadData":{
"SourceDataType":"CSV",
"CSVData":"TUS000721271;Journey Test;R20.0;R132.0;March 2023;Yes! You get INSTANT CASH BACK on selected groceries like bread, milk, nappies and more!",
"Customer":{
"Reference":"TUS000721271-2",
"Name":"Journey Test",
"Surname":"",
"Initials":"",
"Title":"",
"Language":0,
"EmailAddress":"wvermaak86@gmail.com",
"NumberMobile": "0726105303"
},
"Reference":{
"RefAmount1":"20.0",
"RefAmount2":"132.0",
"RefDate1":"March 2023",
"Version":"1"
},
"Distribution":{
"SendSMS":true
},
"ExternalID":1234567890123,
"IsValid":true
}
}

Lastly, the workflow in question is:

GetPDFLinkDetails.bite

Dear Team,

Whenever we copy and paste Assign tool then it is not executing workflow properly.

For example , I have used switch case and in each case I have assign tool having almost same value so I have copy and paster assign tool (I have not dragged from toolbox) and execute the flow ,it was skipping the pasted assign tool.

HelloWorld test cases issue

Hello Team,

In warewolf , Hello world is a default workflow.

Now when we move that to server then error is giving on Hello World test cases as per attached file.(file name :- HelloWorld test cases issue.html)

Then we made test cases for that and added to server to resolve the issue of test cases of Hello World WF.

Again we were facing the same issue and so we delete that test cases and push it to server.

Again error was same.

Now ,we came to know that WW is copying test cases files from program files(x86) to root folder even if we have deleted them from the root folder.

Please resolve this issue as soon as possible. 

I am using WW version 2.8.1.3