Skip to content
Fleans
GitHub

Common Issues

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

There are no known issues at the moment. If you hit one, please open an issue.

Instance shows Failed (or used to sit in Running with no active activities)

Section titled “Instance shows Failed (or used to sit in Running with no active activities)”

Affects: any workflow where an activity fails and nothing handles the error.

Symptom: the instance’s status is Failed (isFailed: true on GET /Instances/{id}/state) and one activity in completedActivities carries an errorState. On releases before the fix for #762 the same situation showed up as an instance stuck in Running with activeActivityIds: [], neither completed nor failed.

Root cause: the failing activity had no error boundary event and no enclosing error event sub-process, so the error ended the last live branch. A frequent trigger is a script task whose script DynamicExpresso cannot parse — e.g. _context.items = new[] { 1, 2, 3 } (implicitly-typed array literals are unsupported).

Fix: read the failing activity’s errorState (also logged at Error level with EventId 1120). Fix the cause — for the array example use new List<object> { 1, 2, 3 } — or attach an error boundary / error event sub-process if the workflow should recover.

Fixtures reproducing this:

Section titled “Related”