Feature Suggestion - Temporarily remove all filters in Workflow Subscriber Trace Log

posted on July 23

The subscriber trace log tries to only show events that match up with starting rules and we have a situation where we have spent 2 months trying to solve missing events.

We tried everything from creating an empty workflow with just an Entry Created / Doc type equals document event to working with LF Support to explain why the events are being filtered out.

The events are in the live trace, but we need them in the trace log so that we can see why a workflow condition is not triggering. The live trace is useless to us as it does not show how it compared the event with the starting condition.

If we could just check a box to include all Entry Created events, then we could save months of time.

0 0

replied on July 23 • Show version history

There are no filters like that. The Subscriber Trace is expected to show ALL events of a given type as long as it has at least one starting rule for the event type. So if you had a rule for "Entry created", you should see all entry creation events regardless of how they evaluated.

The default filter there is that the Subscriber will load the last log file, so you'll get events from the last time the service was restarted or the log rolled over. Older logs are in the WF volume (by default, <ProgramData>\Laserfiche\WF\ServerData\SubscriberLogs\<server name>\<repo UUID>. You have to extract the zip file, then you can load the XML file in the Subscriber Trace.

Edited to add: The Subscriber Trace is always slightly behind the live event viewer because the events only get displayed after they've been processed.

1 0

replied on July 23

Ok maybe I read wrong, I thought if the starting rule was all false it would filter it out based on what I read, I guess it is just saying if there are no starting rules of that type it will filter it out.

So in this case, where it is not showing up that can only mean that it has not been processed. What does it mean to be processed? Just processed by the Subscriber Service to see if any starting conditions evaluate to true?

That means it should show before any events are even sent to the message queue for workflow to pick up on right? If this is the case I don't understand why the technicians are troubleshooting the message queue, that would be outside of the environment.

0 0

Discussion

Discussion

Feature Suggestion - Temporarily remove all filters in Workflow Subscriber Trace Log

Comments 2

Follow-Ups 0

Sign in to reply to this post.