Hi Team, I have workflow which have "Select and apply" tool then i have "Find Record index" tool. I have created test case for this workflow. I found some error. I am attaching the video for that. 

Test Case Creation in ww-2.6.6.mp4

Also input this workflow is object. I am pasting here for sample input 

{
"JourneyName": "Beneficiary Update Journey",
"ReferenceId": "e9b53199-5d99-ec11-b400-000d3a24d450",
"AdditionalData": [
{
"Key": "MandateId",
"Value": "0becaaca-5d99-ec11-b400-000d3a24d450"
},
{
"Key": "CustomerBenefitId",
"Value": "e1ebaaca-5d99-ec11-b400-000d3a24d450"
},

]
}

In warewolf go to setting -> Logging. Set Elastic Source as logging and save it. Restart Server. I am coming back to check my logging source persist or not. but it again set to default. It should be Elastic search source. Here I am attaching video for better understanding.WWSettingLoggingSource.mp4

Created workflow to use redis cache. to test this workflow I have used jmeter.

In Jmeter, out of 10 requests, 2 requests returning blank value for for Redis key. 

Here I have attached video.

https://theunlimited-my.sharepoint.com/:v:/g/personal/wynand_vermaak_theunlimited_co_za/EYEva2n1gjJDibftfg5AN7sBTbk4GywW6W6w_UAYrC670w

I have already tried below Scenarios

Scenario:1

1) Uninstall warewolf existing version

2) Remove Warewolf files from (ProgramData, ProgramFiles (x86), App Data)

3) Restart the system

4) install the warewolf version 2.5.2.88

Scenario:2

1) Install .Net Framework 4.8 

2) Uninstall warewolf existing version

3) Remove Warewolf files from (ProgramData, ProgramFiles (x86), App Data)

4) Restart the system

5) install the warewolf version 2.5.2.88

Scenario:3

1) Update my windows

2) Uninstall warewolf existing version

3) Remove Warewolf files from (ProgramData, ProgramFiles (x86), App Data)

4) Restart the system

5) install the warewolf version 2.5.2.88

Scenario:4

1) Perform the Repair for the warewolf version 2.5.2.88

Scenario:5

1) Restart the Warewolf Service

Scenario:6

1) Install the new version of Warewolf 2.7.1 & Still facing the same issue 

Please find attachment here for server logs. 

ServerLogs

Hi,

I have noticed that All the values of recordset are not passing into child workflow for each loop. I have checked this same behavior into the Select & Apply tool and it's working fine.

Please check the sample attached workflows & issue into screenshot.

forloop_recordset_all_values_not_pass_issue....png
ForLoopIssue-MainWorkflow (1).bite
ForLoopIssue-ChildWorkflow (1).bite

Gandalf 5 months ago

It looks like the For Each is getting confused with 2 different recordset inputs: User(*) and Benefit(*)

Gandalf 5 months ago

Change For Each to use No. of Executes = 3 and see different result. This is from the tool handeling the replacement of * differently and incorectly.

We have checked and found that the sequence of BenifitID in User Payload is incorrect so we changed the sequence and checked the result. Output is coming properly.

Attached are the Edited Workflows.

ForLoopIssue-ChildWorkflow (2).bite
ForLoopIssue-MainWorkflow (2).bite

CSV not working inside a workflow.
Output of workflow should be :For Each with CSV not working.bite
X

Q

X

Q

X

in WW 2.6.10.0, Created sample workflow to test suspend tool and suspended for 10/20 seconds but at the time of resume it is in processing mode for longer period of time and then it is failing in hangfire database. 

below information I got from database.

suspend2.bite

I have video for this bug but not able to attached here. Let me know if you want. (Maya)

Reason
==========================
Execution return TransactionAbortedException: re-queue with caution.


Data:
==============
{"FailedAt":"2021-12-23T09:05:58.6891892Z","ExceptionType":"System.Exception","ExceptionMessage":"The transaction has aborted.","ExceptionDetails":"System.Exception: The transaction has aborted."}


Arguments:
=======================
["{\"resourceID\":{\"m_MaxCapacity\":2147483647,\"Capacity\":36,\"m_StringValue\":\"e5c4d591-dbaa-4b70-b152-86d2b9c06a7a\",\"m_currentThread\":0},\"environment\":{\"m_MaxCapacity\":2147483647,\"Capacity\":122,\"m_StringValue\":\"{\\\"Environment\\\":{\\\"scalars\\\":{\\\"input1\\\":\\\"var1\\\",\\\"input2\\\":\\\"va2\\\"},\\\"record_sets\\\":{},\\\"json_objects\\\":{}},\\\"Errors\\\":[],\\\"AllErrors\\\":[]}\",\"m_currentThread\":0},\"startActivityId\":{\"m_MaxCapacity\":2147483647,\"Capacity\":36,\"m_StringValue\":\"6f2c5415-aaa2-4912-806c-077cfe68ca53\",\"m_currentThread\":0},\"versionNumber\":{\"m_MaxCapacity\":2147483647,\"Capacity\":16,\"m_StringValue\":\"0\",\"m_currentThread\":0},\"currentuserprincipal\":{\"m_MaxCapacity\":2147483647,\"Capacity\":20,\"m_StringValue\":\"CYGNET\\\\mmkhambhayata\",\"m_currentThread\":0}}",null]

Warewolf Version : 2.6.10

Issue Detail : When execute the Main workflow

Please check attached image file

ExecutedWrongly.PNG

You can see the 2 round there is an object "[[@objGetSimStatus]]". I get data properly there. but when I check in decision goes wrongly. I have added condition like If [[@objGetSimStatus()]] Is <> (Not Equal).

You can see 3rd round there shows non existent object { @objGetSimStatus() }

Decision tools have an issue.

I'm also attaching here Server.log file

wareWolf-Server.txt

Warewolf Version : 2.6.8 and 2.6.10

Issue Detail : When I tried to create test cases 

1) It's not display Test name in the left panel where we can see our test cases name ( it happen some time and some time it show)

2) When we see the test cases, there is Assert Mock and Assert Output Label and inside its value field not display properly It should take whole object output value.

3) When I save and run the test case if it has Post tools and mock the value. It display "The source for these tests does not exist. The window will be close when you click Ok"

Please check attached video for more detail.

Unit_TestCase_Issue.mp4

Note: I'm not able to create test case If It has dynamic data.

In newer warewolf version Environment variables are not logged in elastic search. Environment variables are used to troubleshoot workflow errors so it should be logged. 

Suggestion:

-Enable environment variables logging with server setting file configuration
-Mask specific fields in logging