This change takes effect in Sandbox environments on May 31, 2026 and in Production environments on June 7, 2026. Ensure that any required journey or application logic changes are completed before the effective dates.
As part of ongoing improvements to journey branching behavior, we are updating how cancel branches are handled for user-facing steps.
Today, user-facing steps (such as Login Form, OTP, etc.) return a cancel option in the client SDK response even when no explicit cancel branch is configured in the step:
idoResponse.clientResponseOptions?.['cancel']
idoResponse.clientResponseOptions?.[ClientResponseOptionType.Cancel]Moving forward, cancel will only be exposed when an explicit cancel branch is configured on the step. This change corrects behavior to align with the intended journey configuration model and branching logic.
| Environment | Date |
|---|---|
| Sandbox | May 31, 2026 |
| Production | June 7, 2026 |
This change affects applications that rely on the cancel option being returned from user-facing steps without an explicit cancel branch configured in the journey.
If your steps already have an explicit cancel branch configured (e.g., "Go to Cancel Branch"), no action is required. Existing configured cancel behavior will continue to function and will be preserved as a custom branch during a migration performed by Transmit Security.
For cases where no explicit cancel branch is defined on the step but your application code relies on the cancel option being returned:
- Open the affected journey in the Admin Portal (B2C Identity or B2B Identity > Journeys).
- Select the user-facing step that currently returns a cancel option without explicit configuration.
- Add an explicit cancel branch through the alternative/custom branch settings on the step.
- Save and publish the journey.
- Verify that your application handles the cancel response as expected.
Repeat for each step and journey where your code depends on the cancel option.