Listrunner crew macro log not complete due to conversion error

Question

I am using listrunner to run through dozens of workflows.  The workflows run fine but for a small number of them - the listrunner tool reports that they have failed but the workflows results are within expectations but I have noticed that after running the listrunner log through the logparser macro the log is incomplete.

Below is a simple representation of the workflow. Sample data is used to create a csv file for ISO 8859-1 encoding

The next image shows three things:
1. The log when I ran the workflow as a test – showing that the workflow runs.
2. The summary output from Listrunner - showing that the workflow has failed but shows no errors or time
3. Log from listrunner after using Logparser crew macro – shows on comparison of the two logs the listrunner log is missing the "Output data" tool bit which would be tool id 2 and does not show that the workflow has finished as it is missing the “Finished Running” line.

It looks like a conversion error happened when converting wstring to string (as csv encoding is ISO 8859-1 latin) due to the "em-dash" character in the shown string. I am not concerned by the conversion error but it looks like the conversion has affected listrunner capturing the rest of the log.  As listrunner has not recorded the “Finished Running” line it does not know that the workflow finished.

Does anyone know if it is possible to set listrunner to record the complete log perhaps editing one of the crew macros?

Willox · Answer

I'm also experiencing this exact issue. Using the Runner macro rather than the ListRunner but otherwise my issue is identical and not resolved by using the most recent CReW macro set.

The runner tool is reporting that the workflow has failed to run, despite the desired output being generated and no error message coming up in the Log Parser or when running the workflow alone in Designer. The log when viewed in the parser is truncated and I note that the output of runner suggests a time of 00:00:00 which is obviously not the case.

EDIT: I delved into the macro itself and I can see that the log is stopping dead at a field conversion error containing a special character which is obviously similar to what is happening with the issue being discussed above

MarqueeCrew · Answer

@jmulholland ,

Can you please test using this updated version of the macro?  I made a "simple" change to the macro hoping that it would not require a RegEx change to allow for the character encoding.  Please let me know your results.

Cheers,

Mark

CReW_LogParser (test).yxmc