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

Discussion

Discussion

On-Prem Workflow- How do you see if the Subscriber is Online or Offline in Adminsitration Console?

Workflow
Updated November 10, 2022
posted on September 28, 2022

I often need to troubleshoot why workflows are not starting, After a report from users that "things are not moving", I can see in the subscriber trace log that there are no recent events listed and I can re-start the Subscriber service to turn the Subscriber back on so that it processes all the recent events.

There is always some error before the last event which causes the subscriber to shut down, like SQL disconnect or session reset. But the service itself remains running, so where do we see officially if the subscriber is online or offline besides just checking the trace log and noticing that days of events are missing.

0 0
replied on September 28, 2022

The best way to check if the subscriber is connected to the repository is the Laserfiche Admin Console. There should be at least one session from WFUser$ coming from the Subscriber machine.

The best way to check if the subscriber is connected to the WFServer is the "Rule update time" in the Subscriber Trace. The Subscriber checks for updates every 30 seconds.

1 0
View 1 previous reply
replied on September 28, 2022

Ok, I can check for empty WFUser$ connections next time it happens too, it would be helpful if it was more clear that the subscriber was stopped though. For example a little red stop sign next to the icon of the subscriber.

0 0
replied on November 9, 2022

How can we monitor this with Powershell or something that can notify someone that it has gone offline so that they do not lose all their automation activities?

About 20 clients now have reported this to us. I contacted support this time and they said there is no way to know why the subscriber went offline since there is nothing in the logs that provides any details. It just goes offline without reason or error.

0 0
replied on November 9, 2022

Do you have case numbers? I'm only seeing one for your company and it does not have any logs attached to it.

We haven't seen reports of the subscriber stopping event processing. Definitely nothing on the scale you're reporting. Please open cases when you run into the issue, attach the Logs folder and indicate the time frame when the issue occurred.

The both the Workflow Server and the Subscriber emit performance counters, so you could monitor those and alert if you see long periods of no activity.

Probably worth mentioning that the Subscriber will catch up on activity that happens since the last time it was connected.

0 0
replied on November 10, 2022

Case 227918, I uploaded all the logs taken yesterday for the ticket. Nothing was showing any issues in the subscriber error log, I restarted the service multiple times and the log was clear. The only error we had was in the general log which was that "the object's connection was not set", but never specified which object. An object could be anything and is not specific enough for us.

The subscriber catching up on activity is true, but the problem I have is that it only catches up on some small chunk of activity over the entire duration. I have verified this in every case where it was offline for a long duration. Only the latest events are taken account for after bringing it back online.

I can verify this simply by entry creation dates for a well known old workflows which have starting rules on entry created, workflows that have not been touched in ages and were working all the way up to the event. Those entries are not processed at all, not evaluated at all unless they are very new.

It seems the queue for events while the subscriber is down has a rollover, and the other events just get dumped. This is the worst part of it all. If it really did process all events after coming back online it would simply be an outage, not a loss of information.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...