Troubleshooting branch key errors in a Journey batch test
When you run a batch test application through a Journey, you may see the following error:
The specified branch keys do not match the branches of the Journey.
This error means that one or more branch_name values in your uploaded CSV do not exactly match the branch keys configured in the selected Journey.
Why a branch name is required
Every Journey has at least one branch. Alloy requires the branch to be specified for each test application so it knows which Journey path to use.
This requirement applies even when the Journey has only one branch.
Add the branch name to your CSV
Your CSV must include a branch_name column. Enter the exact branch key configured in the Journey for every row.
For example, if the Journey branch is configured as persons, the CSV should include:
first_name,last_name,branch_name Jane,Doe,persons
The branch key is case-sensitive. Spelling, capitalization, and spaces must match exactly.
For example, if the configured branch key is persons, these values do not match:
Personspersonpersonswith a trailing spaceA physical location or organization branch name that is not configured as a Journey branch
Find the correct branch key
Before uploading the CSV:
Open the Journey you selected for the batch test.
Review the branch names configured in the Journey.
Copy the branch key exactly as it appears.
Add that value to the
branch_namecolumn for each CSV row.Upload the CSV and run the test again.
If the Journey has multiple branches
Use the branch key that corresponds to the path you want each test application to follow. Each row can specify a different branch, as long as every value matches a branch configured in the selected Journey.
If the error continues
Check the following:
The CSV header is
branch_name.Every row contains a branch value.
The branch value matches the selected Journey’s configured branch key exactly.
You are testing the intended Journey and version.
The branch value does not contain extra spaces or different capitalization.
If the issue persists, contact Alloy Support with the Journey name, Journey version, and the branch values included in the CSV.
