You are viewing limited content. For full access, please sign in.

Question

Question

Workflow Subscriber Trace Log

asked on April 9, 2014

Hi all,

 

I have a question. How much information does the Workflow Trace Log maintain?

I am trying to troubleshoot what happened with an instance of a Workflow. If the activity happened more than a couple of hours ago, i wont show up in the Subscriber Trace Log.

For instance, sometimes i want to know if an instance has been moved to a certain folder manually by a user, of through a Workflow. If this activity happened recently  i can see it on the Trace Log. Otherwise, it is impossible to know what happened.

Should the Trace Log keep more information or this example can be achieve using another tool?

 

Cheers,

 

Andres

 

0 0

Answer

APPROVED ANSWER
replied on April 10, 2014

The older logs are usually archived on disk. You can typically find them in the following location: c:\programdata\Laserfiche\WF\ServerData\SubscriberLogs\subscriberMachineName\repositoryGuid

 

The logs will be in zip folders named for the range of sequence numbers (event ids) they contain. The logs usually have about 1000 events each in them.

0 0

Replies

replied on April 14, 2014

Hi Ed,

Really good info. Thanks a lot.

And i can also import the XML files into the subscriber to easily read them.

 

0 0
replied on June 26, 2014

Is it possible to extend how long the logs are visible in the admin console without having to load the trace files?

0 0
replied on June 27, 2014

Not at this time.

0 0
replied on September 13, 2018

@████████

Would it be possible to add a feature request to have the system automatically pull in old trace logs based on the search criteria? Or provide a way to browser/load these archives from a remote machine running the WF admin console?

Like many people, I am the application admin, but I don't have access to the server. Hiding these logs on the server makes my life very difficult. If we can find a way to access this data w/o needing access to the server's file structure, that would be ideal.

0 0
replied on September 13, 2018

I can definitely add it to the list.

The logs get saved in the Workflow volume (by default under C:\ProgramData\Laserfiche\WF) under <volume path>\SubscriberLogs\SUBSCRIBER NAME in subfolders named after the repository UUID. For now, you could share the SubscriberLogs folder and make it readable over the network to the appropriate people.

0 0
replied on April 15, 2019

I am also in the same boat as Kenny Fox and would like the Subscriber Trace Log to allow me to view them for more than just a few days before they get archived to the server.  Just like the Audit Trail Reporting feature, I was hoping there was a spot where I could go and change how many days it keeps the data for.  My subscriber trace log appears to be set for 3 days and the WF I was wanting to view had run 4 days ago.  :(

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.