Skip to main content
Find the symptom you are seeing, then follow the checks in order. Most P2HS issues fall into project configuration, build state, deployment configuration, integration credentials, or application runtime configuration.

Projects and source

Source import, revisions, synchronization, and project configuration.

Builds and P2HS AI

Builds that do not start, wait for input, fail, or appear incomplete.

Preview

Preview availability, stale revisions, and runtime behavior.

Deployments and domains

Production deployments, custom domains, DNS, and certificates.

Integrations

Connections, credentials, actions, webhooks, and inbound sync.

GitHub

Repository visibility, permissions, branches, and source updates.

Authentication and forms

Sign-in, sessions, forms, validation, and application data.

BYOK

Customer-managed AI credentials and provider connections.

MCP and AI clients

Client connection, grants, tools, and build visibility.

Billing and AI credits

Estimates, credit availability, and build execution decisions.

​
Still need help?

Before contacting support, collect:
  • project ID;
  • build or run ID, if applicable;
  • deployment ID, if applicable;
  • approximate time of the issue;
  • visible P2HS error message;
  • affected environment;
  • connector name, if applicable;
  • steps to reproduce.
Never send passwords, API keys, access tokens, private keys, or other secret values in a support request.
Use the focused pages above before retrying or reconnecting. They explain when a retry is appropriate and when configuration or support escalation is required.