Question

Workflow with disabled rule still running

Laserfiche Workflow Administration

Updated June 15, 2023

asked on July 24, 2017

I've got an interesting one this morning. I have a workflow for which all starting rules/schedules are disabled. This was done on 7/21/17. I came into the office this morning to see that this workflow had run on it's old daily schedule over the weekend. Additionally, it was running an old version of the workflow (version 78 as opposed to the current version 109). Is there a way to forcibly re-sync rules/schedules for this sort of thing?

0 0

Answer

SELECTED ANSWER

replied on July 25, 2017

The rules are not versioned. However, since you mentioned schedules, you might want to check Windows Tasks Scheduler. You'll need to turn on "show hidden tasks" and look for the schedules that start with "WF8". They should match the active/inactive status you set in Workflow. Depending on the OS version, there's a chance the Workflow server's service user might not have rights to properly disable the schedule.

0 0

Replies

replied on July 24, 2017

Have you tried restarting the Workflow and Workflow Subscriber services on the server?

0 0

replied on July 24, 2017

Yes, afraid that didn't help.

0 0

replied on July 24, 2017

Are these workflows long running jobs or did they start since the changes took place? What is the "start time" on the running workflows?

0 0

replied on July 24, 2017

These workflows had been running properly for a few weeks, however they have been tweaked a bit each day, since they are still in the "set-up" phase. Friday was the first day that I noticed the issues with versions not updating, and rule updates not taking effect.

0 0

replied on July 24, 2017

New workflow instances always start on the latest version of definition. Any chance the SQL database was reverted to an older version?

0 0

View 2 previous replies

replied on July 24, 2017

Yes, they should always run the latest version. Which is why I'm thinking that maybe an old copy was saved somewhere and it's looking in the wrong location. I've verified the network path of the saved file though and tried republishing multiple times. The version number is updating to 79, 80, etc, rather than increasing from the version 109 shown in the workflow's actual properties in the canvas.

0 0

replied on July 24, 2017

The Workflow Server only looks in one place for the Workflow definition, the SQL database. Locally saved copies are not used for starting workflows.

The version shown on the canvas is the file version, not the published version. If you make edits and save it locally without publishing, the file version can drift from the published version significantly. The published version only get increased when a workflow is successfully published.

0 0

replied on July 24, 2017

Okay, well it's not that I'm overly concerned about the version number itself, I can live with those not matching. But I always republish when I save a new version. So I guess I'm not understanding why the starting rules aren't being enforced/updated properly. If I had a workflow disabled, how was it running at all?

0 0

SELECTED ANSWER

replied on July 25, 2017

0 0

replied on July 25, 2017

I think this is the issue! The Windows Task Scheduler shows these as "Ready" whereas the Workflow Designer shows "Disabled". Will look into the account permissions. Thank you!!!

Capture.PNG (33.44 KB)

| Download

0 0

replied on June 8, 2023

Hi All,

Circling back to this, I've discovered what I think is a bug. In the rule manager tab. If you right click and disable the starting rule like this:-

The rule isn't actually disabled even though it shows a red x.

If you double click the red x and green tick to toggle the rule on and off this does work. There seems to be a bug whereby if you use the right click method, it doesn't disable the rule, and it still fires.

Happy to raise this as a support case if it's easier.

Cheers!

Chris Douglas

0 0

replied on June 15, 2023

Could you check if the underlying Windows scheduled task gets enabled/disabled too when you flip the status on a scheduled workflow?

The task will be named something like WF8_<server_Name>_WF<id>_R<id> which you can get from the Schedules node in the Workflow Admin Console.

0 0

replied on June 15, 2023

Hey Miruna,

This wasn't a scheduled starting rule, it was a conditional rule, and it did show as disabled in the WF admin console too, but was still firing!

Cheers!

0 0

You are not allowed to follow up in this post.

Question

Question

Workflow with disabled rule still running

Answer

Replies

Sign in to reply to this post.