Output collection variable is null in error boundary event when sequential multi-instance activity end with error event

Camunda 8 Topics
1

Dear Sir,

If sequential multi-instance activity end with error event, after catching the error boundary event, the output collection variable is null.

How to collect output (even with some error data) in above case?

2

Multi-instance | Camunda 8 Docs mentions words below. Would you like to change the behavior so that we can get partial output?

When an interrupting boundary event is triggered, the multi-instance body and all active instances are terminated. The outputCollection variable is not propagated to the parent scope (i.e. no partial output).

When a non-interrupting boundary event is triggered, the instances are not affected. The activities at the outgoing path have no access to the local variables since they are bound to the multi-instance activity.