Skip to main content

​
Deployment failed

Confirm that a usable source/build revision exists, then inspect deployment configuration, required project settings, environment values, secrets policy, and the deployment timeline. Retry after correcting the visible cause.

​
Production still shows the previous version

Check the latest production deployment, the revision it contains, and its status. Preview changes are not production changes until a production deployment is created successfully.

​
Production works but one feature fails

Check environment-specific configuration, connector binding, application authentication, and the backend capability used by that feature. A successful deployment does not prove that every optional integration is configured.

​
Deployment succeeds but the site does not load

Check the deployment status, domain binding, DNS configuration, and the application error visible through approved P2HS diagnostics. Keep the investigation at the project, deployment, domain, and runtime level.

​
Custom domain remains pending

Review the DNS records shown in the domain configuration, including record name and value. Check for conflicting records and allow time for DNS propagation; the product currently notes that propagation can take up to 24 hours.

​
Domain resolves to the wrong site

Check which project and environment own the domain, remove stale or duplicate records, and confirm the current domain binding in P2HS.

​
HTTPS or certificate is not ready

Certificate provisioning begins after the domain configuration is valid. Resolve DNS and ownership verification first, then recheck the domain status. Related: Deployments, Domains.