There is a send task to create an instance of another process.
Added an event-based gateway with Message Intermediate Catch Event and Timer Intermediate Catch Event
When the process starts and the Timer Intermediate Catch Event triggers, the next task becomes the manual task called "No Response." At this point, both the event-based gateway and the "No Response" manual task are highlighted in yellow. https://dev.app.spiff.status.im/i/5964
After completing the "No Response" manual task, the process instance went to waiting status (which is expected to be as complete), and the event-based gateway was still highlighted in yellow. https://dev.app.spiff.status.im/i/5959
In the library unit tests, the gateway definitely completes when one of the events is complete. So I guess the problem here is syncing the workflow state to the db.
Sample model - https://dev.app.spiff.status.im/process-models/misc:qa:simple-event-based-gateway On this model
When the process starts and the Timer Intermediate Catch Event triggers, the next task becomes the manual task called "No Response." At this point, both the event-based gateway and the "No Response" manual task are highlighted in yellow. https://dev.app.spiff.status.im/i/5964
After completing the "No Response" manual task, the process instance went to waiting status (which is expected to be as complete), and the event-based gateway was still highlighted in yellow. https://dev.app.spiff.status.im/i/5959