Client SDK
Mobile approve
SSO
Sub-journey
Reactivates a device, activates its cryptographic keys, and unlocks associated device-bound authenticators
This step restores a suspended device to Active status, allowing it to be used in journeys again. Reactivating a device also restores its linked credentials to their pre-suspension state:
- Device cryptographic keys associated with the device are activated — but only if they were active before the suspension.
- Device-bound authenticators (mobile biometrics and PIN) that were locked when the device was suspended are unlocked — but only if they were active before the suspension. Authenticators that were independently locked prior to the device being suspended remain locked.
Note
If the device is already active, the step returns an error.
| Field | Description |
|---|---|
| User auth state | Indicates if the user has authenticated in this journey. If the user is authenticated (default), the user context is provided implicitly by the journey. If not, a user identifier must be configured. |
| Identifiers | Only configured if the journey doesn't authenticate the user before invoking this step. Can be an external user ID, email, phone number, username, or a custom identifier, if configured for B2C users in your tenant. |
| Device source | Specifies a device. Defines whether to obtain the device ID from the journey context or specify it explicitly for this step. For more, see Device context. |
| Error output variable | Name of the variable that stores any errors returned by the action |
| Failure behavior | Determines the behavior in case of failure, which either aborts the journey (default) or proceeds to a failure branch of the control flow. |
Journey event data
This step can be configured to record step input and output data, or a custom payload, which is then surfaced in journey events in Journey Analytics for diagnostic purposes. For details, see Additional data reporting.