-
Type:
Feature Request
-
Resolution: Unresolved
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: engine
-
None
User Story (Required on creation):
Currently, messages can only be successfully correlated if the process instance is already in the receiving state. This is sometimes hard to ensure for users and leads to complex workarounds in practice.
Functional Requirements (Required before implementation):
- to be specified: could be similar to the Zeebe mechanism (i.e. TTL on messages that are submitted but not immediately correlated)
Technical Requirements (Required before implementation):
- The synchronization between sender and receiver must be robust and work in all possible race conditions
Limitations of Scope (Optional):
- There may be limitations of the feature to ensure that the implementation is efficient (especially when a new message event is entered, it has to check the message buffer which can be large)