Deployment troubleshooting

Use the deployment status and logs to determine which stage failed.

A deployment did not start

Check:

• The repository is still connected
• The Git provider webhook is active
• The commit was pushed to the connected repository
• The project is not blocked for that environment (paused projects block new production deploys; workspace suspension blocks all deploys)
• Skip unaffected deployments did not mark the push as Skipped because files outside the project root changed only

If the Git provider delivered the event but Easel did not create a deployment, include the repository, branch, commit SHA, and webhook delivery time when contacting support.

A deployment is stuck in Queued

A deployment may remain queued while waiting for build capacity.

Check the Easel status page and whether other builds in the workspace are still running. You can cancel a queued deployment from the deployment detail page.

A build failed

Open the build logs and locate the first relevant error.

Common causes include:

• Dependency installation failure
• Unsupported runtime version
• Missing environment variables
• Invalid build command
• Wrong root directory
• Framework detection failure
• Out-of-memory termination
• Build timeout
• Ignored build step exiting 0 (shows as Canceled, not Failed)

Reproduce the build locally using the same runtime version and build command where possible.

The deployment is Ready but returns an error

A successful build does not guarantee successful runtime behavior.

Check:

• Function logs
• Runtime environment variables
• Routing configuration
• External service connectivity
• Domain assignment
• Framework adapter compatibility

Test the unique deployment URL before testing a custom domain. If the deployment URL works but the custom domain does not, investigate routing, DNS, or TLS rather than the build. See Domain troubleshooting.

The preview URL still shows an older version

Determine which URL you are using:

• A unique deployment URL never moves
• A stable branch or pull request URL moves only after the latest deployment reaches Ready

Check whether the newest deployment:

• Is still building
• Failed
• Was canceled
• Was skipped
• Belongs to a different branch
• Was created in a different project or workspace

Production still serves the previous deployment

Check whether the new Production deployment is:

• Ready
• Current
• Staged and waiting for manual promotion
• Blocked because Instant Rollback turned auto-assign off
• Associated with the expected production branch

A Ready Production deployment does not become Current when auto-assign is off.

A custom domain points to the wrong deployment

Custom domains follow the current production deployment.

Check:

• The domain is assigned to the correct project
• The expected deployment is Current
• DNS points to Easel
• TLS provisioning completed
• No redirect sends traffic elsewhere
• Cache behavior is not serving an older response

Use the unique deployment URL to separate deployment problems from domain problems.

A project is paused

While a project is paused:

• Production hostnames return HTTP 503 with PROJECT_PAUSED
• Preview hostnames keep working
• New production deployments and production promote/rollback are blocked
• Preview deployments can still be created

An Owner or Admin can turn off Pause production in Project settings.

A workspace is suspended

Workspace suspension blocks deployments and traffic for every project in the workspace, including previews. Visitors see HTTP 503 with WORKSPACE_SUSPENDED. Workspace owners cannot clear suspension themselves; contact support or settle billing when the banner points there.

Information to include in a support request

Include:

• Workspace and project
• Deployment ID
• Deployment URL
• Git branch and commit SHA
• Approximate time
• Build or runtime logs
• Reproduction steps
• Whether the issue affects Preview, Production, or both