> ## Documentation Index
> Fetch the complete documentation index at: https://docs.p2hs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Find the right diagnostic path for project, build, deployment, integration, and runtime problems.

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.

<CardGroup cols={2}>
  <Card title="Projects and source" icon="folder-git-2" href="/content/support/troubleshooting/projects-source">
    Source import, revisions, synchronization, and project configuration.
  </Card>

  <Card title="Builds and P2HS AI" icon="hammer" href="/content/support/troubleshooting/builds">
    Builds that do not start, wait for input, fail, or appear incomplete.
  </Card>

  <Card title="Preview" icon="eye" href="/content/support/troubleshooting/preview">
    Preview availability, stale revisions, and runtime behavior.
  </Card>

  <Card title="Deployments and domains" icon="globe" href="/content/support/troubleshooting/deployments-domains">
    Production deployments, custom domains, DNS, and certificates.
  </Card>

  <Card title="Integrations" icon="plug" href="/content/support/troubleshooting/integrations">
    Connections, credentials, actions, webhooks, and inbound sync.
  </Card>

  <Card title="GitHub" icon="github" href="/content/support/troubleshooting/github">
    Repository visibility, permissions, branches, and source updates.
  </Card>

  <Card title="Authentication and forms" icon="lock" href="/content/support/troubleshooting/authentication-forms">
    Sign-in, sessions, forms, validation, and application data.
  </Card>

  <Card title="BYOK" icon="key-round" href="/content/support/troubleshooting/byok">
    Customer-managed AI credentials and provider connections.
  </Card>

  <Card title="MCP and AI clients" icon="bot" href="/content/support/troubleshooting/mcp">
    Client connection, grants, tools, and build visibility.
  </Card>

  <Card title="Billing and AI credits" icon="coins" href="/content/support/troubleshooting/billing-credits">
    Estimates, credit availability, and build execution decisions.
  </Card>
</CardGroup>

## 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.

<Warning>
  Never send passwords, API keys, access tokens, private keys, or other secret values in a support request.
</Warning>

Use the focused pages above before retrying or reconnecting. They explain when a retry is appropriate and when configuration or support escalation is required.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.