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

Question

Question

Workflow Designer not showing workflows running on their schedule

asked on June 3 Show version history

When checking the schedule and history in the administration console for workflows scheduled to run it shows that the workflows are running.

For example here is a workflow that runs every hour throughout the day and the last time it ran was supposed to be at 11am this morning (about 30 mins ago)

However if we view workflow history in the designer, we see there is no instance showing the workflow ran. The one instance from 8:52 was a manual run because the customer needed to get the workflow going at least once today as none of their scheduled workflows are running

Version 12.0.2503.2695

0 0

Replies

replied on June 3

Is this workflow in single instance mode?

If you look at the schedule's history under Windows Task Scheduler, does it show any errors?

1 0
replied on June 4

No single instance mode.

I checked task scheduler and it showed an error for all the workflows

Seems there is a breakdown in communication between task scheduler and WF admin console since it was not displaying this error and said the workflows started on time.

In the task I could go to the actions and see what file is missing

Sure enough it was not there.

There are 2 workflow folders in the Laserfiche program files folder (not just in this environment, this seems to be a default for the install wizard)

One is called Workflow and one is called Laserfiche Workflow 10.4, both created by the installer, not manually for any reason. Workflow is the only product that has 2 folders and uses a number on one of them. Seems the software is trying to keep 10.4 feature backwards compatibility all through versions 11 and 12.

I checked the Workflow folder and I found the executable it was looking for, then I copied it along with the config file to the Laserfiche Workflow 10.4 folder.

After this I tried manually running some tasks in Task Scheduler and it did start the workflow. This may have fixed it but not sure why we need 2 copies of the executable.

0 0
replied two days ago

Hi Chad,

Bug #595144 is filed for this issue. We will investigate and fix it soon.

1 0
replied one day ago

Just came across this on another system and copied the 2 missing files over again. How am I the only one running into this?

0 0
replied one day ago

I have only upgraded one of my Workflow servers to version 12, but it is in our dev environment, and we don't leave schedules turned on. I'll see if I can recreate the issue though.

0 0
replied on June 4

I ran into a similar problem when I set up a workflow to run every hour on weekdays.  It turned out that using the two types of scheduling together created a conflict.  When I set it up to run with five separate schedules (one for each day of the week) every hour, it worked (and still works) fine.

0 0
replied two days ago

Hi James,

Could you please provide the workflow server version and the schedule definitions that will produce the problem?

0 0
replied two days ago

The problem existed at the initial implementation which was years ago.  The problem existed when I attempted to have the workflow run Monday through Friday every 15 minutes for 10 hours.  Here is the scheduling that works.

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

Sign in to reply to this post.