Error when using fork as first activity in workflow
In Adobe Campaign Managed Cloud, an error occurs when a workflow starts with a fork activity. The workflow fails because the fork activity requires an inbound transition. To fix this issue, add a valid initial activity before the fork.
Description description
Environment
- Products: Adobe Campaign Managed Cloud, v7, Adobe Campaign Standard
- Constraints: Fork activity must have one inbound transition
Issue/Symptoms
Executing a workflow with a fork as the first activity results in an error stating that the fork must have one and only one inbound transition.
Resolution resolution
To fix this issue, follow these steps:
- Open the affected workflow in Adobe Campaign.
- Remove the fork activity as the first step.
- Add a start, scheduler, external signal, or another upstream targeting activity such as a query or read audience or list as the initial step.
- Connect the new initial activity to the fork so that it has exactly one inbound transition.
- Save and execute the workflow.
- Verify that the workflow runs successfully without errors.
Note:
The fork activity cannot be used as the first step in a workflow. It requires exactly one inbound transition from another activity.
3d58f420-19b5-47a0-a122-5c9dab55ec7f