Server crashes after clicking “Next” in a workflow. This happens in the situation when there is an error in the workflow. So the expected behavior is logging the exception and displaying the error to the user.
Is there a more thorough description of the conditions leading to this? I suppose not every workflow error causes a server crash. It is important for future understanding of why this change occured.
The problem was reported in a workflow with a ui task.
We should add a comment to the code explaining where the exceprion gets handled.
Let’s model some tests on this:
Basic workflows
- Workflow with 1 step that fails
- Workflow with 2 steps where 2nd step fails
- Workflow with one UI step and another next step, which fails
Subworkflow tests
- Workflow without UI with a subworkflow call using call workflow method - calling all basic workflows
- The same as above but using call workflow using service call
- Workflow with a UI step and after calling a subworkflow call using call workflow method - calling all basic workflows
- The same as above but using call workflow using service call
In total 15 tests should run.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.