Skip to content

Recover a failed deploy

Check whether the previous release still serves traffic. Identify what failed before choosing a rollback or a targeted fix.

View Markdown

Find the failure#

Record the account, project, deployment ID, source revision, and affected URL. Reproduce the failing action and read its logs with secrets and personal data removed.

SignalCheck first
Build failedBuild logs and the last successful revision
Published app returns errorsRuntime logs, bindings, and data compatibility
URL serves the wrong buildProject, route, domain, and deployment target
Provider returns an errorAccount, resource, permissions, and provider status

If you need credentials, pin the task's setup and read the provider guide before using its recovery tools.

Restore service#

Fix a reversible configuration error at its source. For a rollback, choose a known working release and check what the provider restores. Database changes, queues, and external writes can outlast a code rollback.

Check the recovery#

Open the affected URL, confirm the intended release, and repeat the failing action. Test the main related flow and record the cause, fix, and remaining impact.

Fix account access#

Check which account the tool uses and whether the credential can access the intended resource. For an expired or revoked credential, follow the provider's rotation steps and update each affected host or deployment. See Credentials and native logins.

Godmode v0.20.0 · 2026-11-19 · Inspect the source · Get help