That is very strange and uncommon behavior . In your IS log do you see something like Starting scheduled run of the workflow.
Can you share a snapshot of the scheduler tab from workflow manager .
The only thing which I could imagine is that this particular workflow was once set to Run On Server Initialisation and that it has been changed to Run On Demand at some later time. That MAY explain this behaviour.
Still this looks like an error to me, so - as mentioned by Santosh - I can only recommend to examine the Integration Service logs for any messages about this workflow.
In addition to the reply of Nico I can think of one other option.
The workflow was scheduled and in the workflow manager you changed the workflow to run on demand but did you also un-schedule the workflow?If you make scheduling changes to a workflow it is a best practise to always un-schedule and (try to) schedule a worklow again.
Especially when the workflow was scheduled to run on Monday and you didn't un-schedule it the described behaviour makes sense to me.
1 of 1 people found this helpful
Could you share the more details on it. Can you check all the nodes having same shared configuration on it?