Merge Parallel Steps

These actions provide ability to merge parallel saga steps in distributed flow executions.

Merge Parallel Steps Actions

Merge

Merges multiple parallel running branches in a saga flow, storing merge status in a state manager. Each merge instance is identified by a unique taskId, and contributing branches are identified by their mergeIds. When all required merge ids are received, the merge step continues.

Table

Field	Definition	Example	Default
Domain	Name of state manager for coordinating merge state	search_merge	-

JSON Schema

With event metadata parameters as:

Table

Parameter	Definition	Example	Default
Merge Path	Json path of the payload that should be merged with other merge branches	results	-
Required Merge Ids	Comma separated list of merge ids that are required to complete the merge	1,2,3	-
Merge Id Path	Json path which defines id for merge branch	id	mergeId
Task Id Path	Json path which defines id for merge instance	mainId	taskId

JSON Schema

In local saga flows, steps run in sequence. Use ForEachEventHandler to create parallelism there instead of MergeEventHandler.