telep forge · support
support.
the failures we know about and how to get past them. if yours is not here, get in touch.
the github app is installed but forge says it has no repository access
- Choose Refresh connections. Forge re-reads your installations rather than waiting for a callback.
- Confirm you installed the app on your personal account, not an organization. Organization installations are not supported for repository creation.
- If you limited the installation to selected repositories, that is fine. Repositories Forge creates are added to the installation automatically.
- If it still does not appear, open GitHub's installed apps settings, confirm the Forge app is listed under your account, then refresh connections again.
vercel cannot import or build the repository
Vercel reaches GitHub through its own integration, Vercel for GitHub. The Forge app cannot grant that access for it.
- Install Vercel for GitHub on your GitHub account if you have not already.
- In GitHub, open the Vercel app under installed apps and make sure it can read the website repository. If its access is limited to selected repositories, add this one.
- Back in Forge, choose Retry deployment.
"wrong team" or a project that must use its owning team
A website that has already been linked to a Vercel project must keep deploying to the account or team that owns that project. Forge checks this before it writes anything to GitHub.
- Choose Change account and reconnect Vercel, picking the account or team that owns the existing project.
- If you meant to move the site to a different team, that is not something Forge can do today. Create a new website in Forge for the new team, or move the project inside Vercel and contact us.
the build or checks failed
- A failed check blocks the new production deployment. Your repository and your saved draft are kept, so nothing is lost.
- Open the deployment in Vercel and read the build log. If you have customized renderer code in the repository, the error is usually there.
- Fix the cause, then choose Retry deployment. It publishes the current saved draft to the same repository and Vercel project.
deployment status stopped updating
- If Forge lost contact while polling, choose Retry deployment status. It resumes checking the existing deployment without publishing again.
- If the deployment actually failed or was canceled, Forge shows Retry deployment instead. See failed build above.
- You can always check the deployment directly in the Vercel dashboard.
forge reports a content conflict
This means the content in GitHub changed since Forge last saw it, and your saved draft also changed. Forge will not guess which one you want.
- Choose Download draft first, so you have a copy of your draft no matter what.
- Look at what changed in GitHub. If someone edited the content file directly, decide whether those edits or your draft should win.
- Choose Use GitHub content to replace your draft with GitHub's version, or Keep my draft content to publish your draft over it.
If Forge shows Retry GitHub sync instead, it is a connection problem, not a conflict. Nothing will be replaced. Retry once the connection is back.
the preview does not match the deployed site
If you customized the renderer code in the repository, Forge preserves it but does not execute it on its server. The editor preview uses the stock renderer and shows a warning that it may differ. Use the deployed site on Vercel to check custom rendering. Content edits still flow through to your custom renderer on the next publish.
contact
Reach us through telep.io/contact. Forge is in preview and support is best effort. To help us help you, include:
- the GitHub login you signed in with and the website name;
- what you were doing, roughly when, and the exact message Forge showed;
- the deployment URL or repository name if the problem is on the publishing side.
Never send us your GitHub or Vercel tokens. Forge does not need them and we will not ask for them.