How to Configure the AND-join Activity in Adobe Campaign Classic
Highlight text, then choose “Suggest an edit”.Your selection is saved in the bottom bar.
Adobe Campaign Classic’s AND-join activity synchronizes workflow branches by waiting until all connected incoming transitions have been activated before it activates its downstream transition. Use the AND-join activity where parallel branches must converge before the next activity runs.
How the AND-join Activity Works
An AND-join has multiple incoming transitions and one outgoing transition. It waits until all incoming transitions connected to the activity have been activated. Once they have all reached the AND-join, the data from one selected incoming transition is passed to the outgoing transition.
Start
|
Parallel branches
|---------------- Branch A ----------------|
| |
|---------------- Branch B ----------------|--> AND-join --> Next activityIf Branch A activates first, the AND-join remains waiting. Its downstream transition activates only after Branch B also reaches the join.
The join evaluates connected incoming transitions. A branch that is visually near the activity but not connected to it is not part of the synchronization condition.
Configure the AND-join in a Workflow
- Add an AND-join activity where the parallel branches converge.
- Select primary set that will be transferred to outbound transition
- Connect the outgoing transition from every branch that must reach the synchronization point to the AND-join.
- Connect the AND-join’s downstream transition to the activity that must run after all branches have arrived.
- Save the workflow and review every incoming connection before execution.
The connection layout defines the synchronization condition. Connect only branches that must activate before the downstream activity can proceed.
Hypothetical Example: Waiting for Two Processing Branches
A campaign-audience process has two parallel branches: one enriches customer records and the other validates consent status. The downstream delivery path must wait for both branches.
Audience query
|
Split
/
Enrich Consent validation
/
AND-join
|
DeliveryThe delivery path remains waiting after the enrichment branch reaches the AND-join. It proceeds only when the consent-validation branch also activates its incoming transition.
Conditional Paths Can Leave the Join Waiting
Every incoming transition connected to an AND-join is required for that join to proceed. A conditional design that does not activate one of those transitions leaves the AND-join waiting.
Condition
|------ Path A ------|
|
|------ Path B ------|--> AND-joinDo not connect an optional path to an AND-join unless the workflow design ensures that the path activates for every execution. Otherwise, redesign the branches so that all transitions connected to the join can arrive.
Troubleshooting a Waiting AND-join
When an AND-join does not proceed, trace each incoming connection back through the workflow and confirm that its branch reached the transition connected to the join.
Check these points:
- Every intended branch is connected to the AND-join.
- No required branch bypasses the join.
- Conditional logic has not left a connected incoming transition unactivated.
- The downstream activity is connected to the AND-join output, not directly to an upstream branch.
Keep the AND-join close to the point where its branches converge. This makes it easier to inspect which transitions are part of the synchronization condition and which paths remain independent.
