Pål Edman

In the example above, that is a subset of your diagram, the parallel **join** gateway will wait for all taken/discarded sequence flow before continuing. Hence, the parallel join gateway outbound...

One thing might be that you return without sending a run-format-end message which will stall the execution: ```js if (!response) { // exiting the activate block return false; } ```...

@shaansriv have you resolved the issue?

If I remember correctly you can publish the endRoutingKey with an empty object as message content. The errorRoutingKey should be published with the error as message content property.

Is the activity-handler looking something like this now? ```js return { activate() { bpmnActivity.on("enter", async (elementApi, engineApi) => { const endRoutingKey = 'run.format.complete'; const errorRoutingKey = 'run.format.complete.error'; bpmnActivity.broker.publish('format', 'run.format.start', {...

I also see that the `bpmnActivityHandler` extension doesn't discriminate what activity it is applied to. All activities, processes, etc will have that extension. You should filter which activity it should...

Does running with debug give a hint where it stops? For *ix it's `DEBUG=bpmn* npx mocha -b` or Windows `$env:DEBUG="bpmn*"; npx mocha -b`

In your sequence flow conditions you address e.g `this.environment.amount` and not `this.environment.variables.amount`. Is this intended? Out of curiosity: what modeller do you use?

I have added a test for your sub-process. It runs through "on my computer". Please checkout branch `issue-188`, add your extensions, proper services, etc, and start building tests around it....

For Camunda 7 you can use [@onify/flow-extensions](https://www.npmjs.com/package/@onify/flow-extensions) which has decent feature coverage. For Camunda 8 there are no extension published on npm, AFAIK. But fear not! First of all, the...