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

Question

Question

Subscriber Tracer Starting Rule Threads

asked on December 30, 2022 Show version history

I've been reading through the Workflow help documentation as well as previous presentations from Empower, specifically PDR204 Admin 205 Optimizing System Performance In Laserfiche Forms and Workflow. According to the PowerPoint presentation for that presentation, when you increase the threads in Workflow Admin Console > Advanced Server Options > Monitored Repositories, the Subscriber Tracer should then show a corresponding chart for each thread under Processing Loads. I could be reading into it incorrectly, but that is what I gathered from the slides.

This morning, under Processing Loads, my Starting Rules 1 was pegged at 100%. Taking my newfound knowledge, I increased the Starting Rule thread count from 1 to 2. I closed and reopened the Subscriber Tracer, but I still only showed the Starting Rules 1 (along with Notifications, Parent Conditions 1, Wait Conditions 1, and Wait Conditions 2). So, I increased the thread count to 3, but still no luck. I decreased it back to 2 and have had there for about an hour with no change. I have also tried restarting the Subscriber service.

Should I see a Starting Rules {n} in the Subscriber Tracer each time I add a thread? The help file says the subscriber updates once per minute and tries to wait for the opportune time to make the change. The Starting Rule 1 is now fluctuating, so I can't imagine it is still waiting.

Any help understanding this would be greatly appreciated. We are currently on Workflow 10.4.3.

0 0

Answer

SELECTED ANSWER
replied on December 30, 2022

When you updated the starting rule threads to 2, you updated it for <Default>. What this means is that any new repository that you add to be monitored via the Workflow Configuration Manager will then have 2 starting rule threads.

However, that change won't be applied to any repositories that are already being monitored. What you need to do is to change the "Options for repository" dropdown to the pre-existing repository that was already being monitored. Then change the number of starting rule threads to 2. Then restart the Workflow Subscriber service.

0 0
replied on December 30, 2022

I knew I was forgetting something. That drop-down for repositories always gets me. Thank you, Alex!

1 0

Replies

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

Sign in to reply to this post.