PONSTroubleshooting
Resolve common website, account, execution and publication failures without inventing state.
The website is blank or returns 404
For Vercel, verify that the project imports the repository root and uses Next.js, pnpm build and .next output. The repository’s vercel.json supplies those settings. The Cloudflare build produces a Worker plus assets and is not a standalone static Vercel website.
Check the deployed commit, requested domain and failed network response. A successful deployment record alone does not prove the route is serving HTML. Inspect the actual page and its asset requests before changing unrelated code.
Repositories load but votes or balances do not
Read /api/catalogue and /api/overview. If storageUnavailable is true, research pages are working but persistent services are not connected. The default Node/Vercel runtime currently has no database adapter.
Connect a real durable storage implementation before enabling writes. Do not convert unavailable values into fake vote counts or show locally stored form state as a saved request.
Sign-in fails or a wallet cannot save a request
The wallet and account gateway are independent. Confirm that the gateway handles the existing sign-in route, validates the session and replaces identity headers with a valid opaque ID and matching private secret.
A publicly reachable sign-in URL does not provide authentication by itself. Missing or incorrect gateway configuration remains anonymous. Never resolve this by trusting identity values submitted by the browser.
A repository is rejected
Use a public https://github.com/owner/repository URL without extra paths. Intake rejects private or archived sources and requires a verifiable crypto purpose. GitHub API errors and rate limits can also interrupt a source check.
A saved request can still be blocked at build time if its detected license is outside the automated allowlist. Read the source revision and license evidence instead of changing metadata to bypass the check.
A build stays queued
Check the existing job ID in the runner before dispatching again. A network timeout may have occurred after the runner accepted and started charged work. The app intentionally keeps that reservation held until dispatch and cost are reconciled.
Verify runner reachability, callback authentication, durable storage and provider configuration. A completed artifact with an undelivered callback should trigger callback delivery recovery, not a second model run.
The feed has activity but no public commit
Public events and GitHub publication are separate integrations. Check the configured destination, scoped publisher credential, publication flag and private-term rules. If a content or path check fails, the publisher pauses and emits a generic event.
Inspect the rejection privately. Do not publish raw rejected output, remove privacy controls or expose a token to the sandbox to get a commit through. Confirm whether a partial job branch already exists before retrying publication.
Keep a useful, non-sensitive issue record
Record the affected route, HTTP status, deployed commit and relevant public request or job ID. Include concise reproduction steps and the observed behavior. Keep authorization headers, environment values, private source and provider billing details out of public issues.
For a public code issue, link to the affected source and describe the smallest reproducible failure. Security issues and private operational records need an appropriate private reporting channel.