Auth0 extensibility-related features will execute in one of the available Node extensibility runtimes. Multiple versions of Node extensibility runtimes may be available concurrently, as part of the process of introducing newer versions designed to replace older ones.

• Actions
• Extensibility Runtimes

The process to configure the target runtime version used to execute extensibility varies by extensibility feature type. More specifically, custom database connections, custom social connections, and legacy extensibility (rules and hooks) use the runtimes as defined in the tenant's advanced settings. On the other hand, actions-based extensibility uses the runtime configured individually in each action.

The following sections describe how to use the Dashboard to manage the extensibility runtime version used to execute the various extensibility-based features. Alternatively, use the Auth0 Deploy CLI, Auth0 Terraform Provider, or direct integration with the Management API to manage these settings programmatically. In particular, for actions, the endpoints to update, deploy, and rollback an action would be relevant alongside the update tenant settings endpoint for managing tenant runtimes.

Upgrading custom actions:

1. Navigate to Auth0 Dashboard > Actions > Library.
2. Choose a custom action targeting an outdated runtime.
3. In the warning panel, select Upgrade.
4. Select Deploy to make the runtime upgrade effective.

Downgrading custom actions:

1. Navigate to Auth0 Dashboard > Actions > Library.
2. Choose the custom action.
3. Select Version History.
4. Select the version targeting an older runtime and click Revert.

Managing tenant-level extensibility runtimes:

1. Navigate to Auth0 Dashboard > Settings > Advanced.
2. Locate the Extensibility section and select the desired Runtime version.
3. If the tenant has access to rules and hooks, select its desired Runtime version in the Legacy Extensibility section.
4. Select Save.

When transitioning from a runtime version that has already reached end-of-life to a newer runtime, it may not be possible to downgrade back to the discontinued runtime. Avoid potential problems arising from this situation by planning upgrades to the latest runtime version once new versions are released and by verifying compatibility with newer runtimes in non-production environments before implementing changes to production tenants.