Auth0 Action Deployment Propagation Delay Causes Previous Version Execution

Overview

When a new version of an Auth0 Action or Custom Database script deploys, the previous version executes if authentication occurs immediately. Auth0 uses a snapshot-based architecture that introduces a propagation delay of up to 30 seconds across execution pods. Waiting 30 seconds after deployment ensures the new version executes during the next authentication.

Applies To

  • Auth0
  • Auth0 Actions
  • Custom Database Scripts

Cause

Auth0 utilizes a snapshot-based architecture for the execution pipeline rather than reading directly from the database on every request. A background process polls the database for changes and publishes snapshots to object storage, and each execution pod polls the object storage to refresh its local cache. This architecture creates a propagation window of up to 30 seconds before a newly deployed Action version reaches all pods.

Solution

How does Auth0 establish runtime readiness for a newly deployed Action?

Wait approximately 30 seconds after a successful deployment response before initiating a verification login. This delay provides confidence that all execution pods have updated their local caches with the new snapshot. Auth0 automatically updates the binding to pick up the new version once propagation completes. Auth0 does not require manual trigger re-binding.

 

Review the following screenshot demonstrating the warning message that changes require up to 30 seconds before taking effect.

warning message

 

Verify the executed Action Version Using the Management API

Use the Management API to confirm which version of the Action executed during a specific flow. Call the executions endpoint and review the version identifier in the response to verify the executed Action version.

  1. Call the GET /api/v2/actions/executions/<id> endpoint.
  2. Review the version_id in the response to determine if the new version or the previous version executed.

 

Does the propagation delay affect Custom Database scripts?

The same 30-second propagation limitation applies to Custom Database scripts, including tests that administrators initiate using the Save and Try button for the Get User script.

 

Recommended content

No recommended content found...