Hi,
when checking the Action Description of a failed process flow in the Process Flow Log, the description is cut short and the actual error, which is normally at the end, is not readable. Where can I get a full error log?
Solved
Process Flow Error log incomplete
+1Best answer by Phil Seifert
Hi Jason,
I think then you would have to review the event logs on the server to get more text to this error or perhaps query the wf_audit_triggered table to pull the full information. I suspect there is a limit to how much can be shown/passed to the comments viewer based on your screen as the definition of the wf_audit_triggered.descr column were this information is stored is already max.
I understand this will be problematical for you as you are hosted and do not have access to the database or servers normally & should not leave the event logging going to the database instead of the file system.
I did find one instance today (7-March 2023) with the descr containing %ROUTE_TO_FIELD% in it that was in error so perhaps this is the one you are reviewing? Unfortunately, only 4000 characters was populated and it truncated before seeing more information.
My suggestion is to log a ticket in the IFS Support Partner Portal to investigate if it is possible to expand what is populated into the wf_audit_triggered.descr colum & the comments viewer for this module or not.
Please provide the process flow name and the date/time of the event so this can be investigated further.
+23Hi Jason,
I am presuming you are in the Process Flow Log module and see a list of events when zooming into an error action. From the initial zoom view, if you move the mouse cursor to the dotted square, this will open the comments viewer and you can see all the comments under the action description for that row.
Hope this helps.
+1Hi Phil,
I’m already looking at this view, It’s this view that is cutting off the details of the error at the bottom.
is there another way to get this information.
as you can see from the screenshot the bottom of the info is cut short, and this is where the error of why it failed is.
+23Hi Jason,
I think then you would have to review the event logs on the server to get more text to this error or perhaps query the wf_audit_triggered table to pull the full information. I suspect there is a limit to how much can be shown/passed to the comments viewer based on your screen as the definition of the wf_audit_triggered.descr column were this information is stored is already max.
I understand this will be problematical for you as you are hosted and do not have access to the database or servers normally & should not leave the event logging going to the database instead of the file system.
I did find one instance today (7-March 2023) with the descr containing %ROUTE_TO_FIELD% in it that was in error so perhaps this is the one you are reviewing? Unfortunately, only 4000 characters was populated and it truncated before seeing more information.
My suggestion is to log a ticket in the IFS Support Partner Portal to investigate if it is possible to expand what is populated into the wf_audit_triggered.descr colum & the comments viewer for this module or not.
Please provide the process flow name and the date/time of the event so this can be investigated further.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.