Workflow Subscriber - Control Events That Are Monitored

asked on July 28, 2024

For the majority of our customers, we only build Workflow start rules for when an entry is created, moved, or changed. If we delete thousands of documents, I've noticed that quite a bit of processing goes into Subscriber checking to see if there are any start rules related to the deletion of these documents. Is there a way to control which events specifically subscriber monitors for (e.g. Created, Changed, Moved, ...) so that it doesn't check for start rules against events that we have nothing built for? Or even better, if it knew there were not any start rules tied to the deletion of a document and thus didn't waste any time monitoring for the Delete event?

0 0

replied on July 28, 2024

Hi Beau,

Is there any performance or other issues on Workflow caused by thousands documents deletion? It could make starting rule configuration more complicated and user may feel confusing if we allow this.

0 0

View 2 previous replies

replied on July 29, 2024

It is not a common occurrence but something I thought would be a helpful feature for extremely large customers who rely heavily on Workflow. We run into it with a few large customers where they delete hundreds of thousands of documents and it backs up subscriber checking for all of the delete rules. Not a top requirement but I was hoping it might be something that could be added to the "Advanced Server Options" portion of the Workflow Administration Console for those customers who wanted to streamline their environment even more.

0 0

replied on July 29, 2024

How much of a backup do you see? The Subscriber is not doing any rule evaluations on entry deletion events if there are no starting rules for them.

0 0

replied on July 29, 2024

The subscriber trace log was about 10 minutes behind during this high-volume period of deletions but once it caught up, everything continued fine. Not a huge deal and could possibly be related to a slowdown somewhere else but we just were able to actually see it here. I was just hoping to have Subscriber not even monitor the Delete events so I could narrow down if the issue is here or upstream.

0 0

replied on July 30, 2024

I'd check your other starting rules to ensure they're written efficiently, with the broadest exclusion criteria first. Workflow stops evaluating a starting rule as soon as it can tell the rule won't apply, so the sooner it can figure that out, the sooner it can move on.

0 0

replied on July 30, 2024

The start rules are written correctly. Subscriber shows the Delete event happening and that no rules were tested. It was just taking 10 minutes from the time the event showed in the live event viewer, until it was evaluated by subscriber. The issue only comes up once a year so it isn't the end of the world. I appreciate all of the suggestions.

0 0

Question

Question

Workflow Subscriber - Control Events That Are Monitored

Replies

Sign in to reply to this post.