Workflow moving forward despite tasks not completed

0

Hi,
Do you set in parameters " Operation executed on parallel tasks-> Wait for required task to be completed" ?

Thanks,
Raluca

Hi Mark,
Do both user groups exit the step along the same path?

Hi Raluca,

Yes, of course :) (see attachment)

Hi Jacek

Task creation is based on a form field and tasks get created when the workflow transitions to a path. Did you have something else in mind? Where do I check this?

Thanks!

I asked not about creating a task, but about the path that users exist from the step (finish task)?. Is this the same path or are there multiple exist paths?

Hi Jacek,

There are 3 paths from that step:
-Save, which loops back into the same step
-Back to previous step
-Confirm, which users are supposed to use to complete the task.

Users use the confirm button and in most cases, it works fine. For some people, it transitions into the next step.

Thanks

I suspect the "save" path might be a problem. How is the task assignment set there?
Does the history show that "special users" have previously made a "save"?

Hi,
Are there several paths that go into the same step ?
I'm thinking that tasks from different cases should not be received. There might be a route that hasn't set the path to "Completed-All".

Thanks
Raluca

Or maybe the save path is set to "set other task as finished"?

Hi,
My advice is to monitor an instance that has waited for all approvals and an instance that isn't functioning properly.
Check what the users did differently: which paths they pressed or which route on the workflow they followed.

Thanks,
Raluca

Hi,

The save step has task creation set to "Completion - All" and Parameters set to "Wait for required tasks to be completed" and number of required "All".

Also, up until the point where the workflow started to act funny, no one used the Save path.

Thanks!

Hi Mark,

what you encountered is one of two reasons, I created a form rule to add a "virtual" path button which simulates a click on the save action.
https://daniels-notes.de/posts/2021/unified-save-experience#save-button-as-a-path-button


Best regards,
Daniel

Hi Daniel,

So you are saying the issue is the Save path? We should only use the save action?