In Workflow Manager 10.2.2, we have a workflow where every step is checked as "Step cannot be skipped" in the step properties.
We are seeing some unexpected behaviour. When the workflow is executed, the user can pick any step in the workflow (for example, the third or forth) and right-click to select "Set as Current Step". Once the step is set to the current step, the step can be run successfully. All of the previous steps have been skipped but no warning or error message appears.
Has anyone else experienced this? Thanks!