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):

1. Create diagram with at least to service tasks.
2. Connect service tasks so one is being run after another.
3. Give the first task "after" asynchronous continuation.
4. Make second task throw an exception.
5. Run process.
6. 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.