-
Bug Report
-
Resolution: None
-
L3 - Default
-
None
-
7.16.0
-
None
Environment (Required on creation):
MacOs Monterey 12.5.1, Camunda 7, application with Spring-boot 2.6.8.
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):
A strange behaviour occurs when running a Camunda process which contains “after” asynchronous continuation assigned to a service task. After task A (with “after” asynchronous continuation), we run task B which throws an error. For some reason, the error is displayed in task A instead of task B, despite the fact the task B is at fault here.
Steps to reproduce (Required on creation):
- Create diagram with at least to service tasks.
- Connect service tasks so one is being run after another.
- Give the first task "after" asynchronous continuation.
- Make second task throw an exception.
- Run process.
- Open Camunda UI and view process.
Observed Behavior (Required on creation):
Error appears on the first task instead of the second one.
Expected behavior (Required on creation):
Error should appear on the second task.
Root Cause (Required on prioritization):
Uknown.
