Why it is important? It enables the process to synchronize and control the flow based on the arrival of specific messages, ensuring proper coordination between process instances. Similar to the message catch boundary event, the message catch intermediate event is important because it facilitates the communication and coordination between process instances through messages. By incorporating this event, the process can effectively synchronize and control the flow based on the arrival of specific messages.
Message Catch Intermediate Event can be used as a standalone node, this means that it will block a process until it receives an event.

​
Configuring a message catch intermediate event

Imagine a process where multiple tasks are executed in sequence, but the execution of a particular task depends on the arrival of a certain message. By incorporating a message catch intermediate event after the preceding task, the process will pause until the expected message is received. This ensures that the subsequent task is not executed prematurely and allows for the synchronization of events within the process.

​
General config

  • Can go back? - setting this to true will allow users to return to this step after completing it, when encountering a step with canGoBack false, all steps found behind it will become unavailable
  • Correlate with throwing message events - the dropdown contains all catch messages from the process definitions accessible to the user
  • Correlation key - process key used to establish a correlation between the received message and a specific process instance
  • Receive data - the process key that will be used to store the data received along with the message
  • Stage - assign a stage to the node