Component workflow tokens expire after one (1) year. The tokens of component workflows that are close to expiring or have already expired must be regenerated. Component workflows that are close to expiring will have a warning icon and workflows that have already expired will have a red error icon appearing against the workflow name to make them easily identifiable.
Caution: Regenerating a token replaces the current active token, which will be invalid in 24 hours. Regenerating a token that is revoked or expired will make the component workflow become available for external start again. Ensure to update the external workflows or applications that call the component workflow with the new token, or else they will fail.
Note:
- This option is available only for users with an administrator role.
- Workflows that use the Call a workflow to call a Component workflow are not impacted by the workflow tokens.
-
Open the Component workflow tokens page: Click Settings and then click Component workflow tokens. Component workflows that are close to expiring will have a warning icon and workflows that have already expired will have a red error icon appearing against the workflow name to make them easily identifiable.
- Click
next to the component workflow, and then select {.} API endpoints. The Component workflow dialog is displayed. Note: Alternately, you can open the component workflow dialog from the
Workflows page. Click (Options)

next to the name of the component workflow, and then select
{.} API endpoints.
- Click
next to the Token field and select Regenerate from the menu.
- Click Regenerate to confirm.
The token becomes regenerated and the component workflow is valid for external start again.
- Update the new regenerated token in your application to complete the process.