Skip to content
Fleans

Common Issues

This page documents known bugs and behavior gaps. For the full element-level coverage status, see BPMN Support.

Boundary events on intermediate-catch don’t fire

Section titled “Boundary events on intermediate-catch don’t fire”

Affects: intermediate timer, message, and signal catch events with a boundary event attached.

Symptom: the boundary event never fires. The host activity blocks until something else (cancel, completion, or timeout from a higher scope) interrupts it.

Root cause: boundary subscriptions are not registered when the host is an IntermediateCatchEvent. Boundaries on Tasks, Subprocesses, and Call Activities are unaffected.

Workaround: wrap the intermediate-catch in a single-activity subprocess and attach the boundary event to the subprocess instead.

Fixtures reproducing this issue:

Child-process errors don’t propagate to parent error boundary on CallActivity

Section titled “Child-process errors don’t propagate to parent error boundary on CallActivity”

Affects: call activities with an error boundary event, where the called child process throws an unhandled error.

Symptom: the CallActivity stays in Running state indefinitely. The error boundary event on the parent does not fire.

Root cause: error events emitted from the child workflow don’t trigger the parent’s CallActivity error-boundary subscription.

Workaround: handle the error inside the child process and signal the parent via a normal end event with a discriminator variable. The parent reads the variable and gateway-routes accordingly.

Fixtures reproducing this issue:

Section titled “Related”