Publishing failed: what should I do?
When a TeleportHQ publish fails or is blocked, the message on screen names the reason. Most often it's a build error (open Publish → Deployments → Build Logs), a page or component name the code can't use, a plan limit (forms, languages or a Web App slot), or a temporary problem you can fix by publishing again. A failed publish never replaces the version that's already live. Find your message below.
Where to see that a publish failed
In the TeleportHQ Publish window, on Production, the status at the right of your site's address says Publish failed. A message in the editor explains why.
If the message disappeared before you could read it, click the warning icon at the top right of the editor header. The Recent errors and warnings list shows it again, with a Copy button for support. See What do the warnings at the top of the editor mean?.
The build failed
"The deployment failed while building on Vercel." Something in the project stopped the TeleportHQ site from building. Under From the build log:, the message quotes the log lines that say what broke, and it ends with "Open the Deployments tab → Build Logs for the full log." When TeleportHQ recognises the problem, a Likely cause: comes first, with the fix:
- "An element carries a custom "style" attribute with text in it. Remove that attribute and use the Style panel instead."
- "A text area has both a value binding and text content. Keep one of the two."
To read the whole log:
- In the Publish window, click Deployments on the left.
- Next to the failed deployment (status Error), click ⋮ and choose Build Logs.
- Click Errors only to see the problem, and fix it in the editor.
- Publish again.
See How to read build logs when publishing fails.
"The deployment was canceled before it finished building. Please publish again." Click Publish to Production again.
"Your project built successfully but its address could not be pointed at the new deployment. Please publish again." Publish again. Your previous version stays live until it works.
"Your project is still building on Vercel. It will go live on its own — check the Deployments tab in a few minutes." This isn't an error. Large projects take longer. Check Deployments in a few minutes.
Publishing stopped at "Generating the code"
These TeleportHQ messages start with "Publishing failed." and name something in your project that the code can't use. Fix it, then publish again:
- "…a page or component named "Template", which the generated code reserves for itself." Rename that page or component in the Explorer, for example to
TemplateSection. - "Your project still uses a component called "…" that no longer exists." Recreate the component, or remove the places that use it.
- "A style called "…" is used somewhere in your project but no longer exists." Apply another style, or recreate the one that's missing.
- "A design token called "…" is used in your styles but no longer exists." Recreate the saved value (for example a saved color), or change the styles that use it.
Publishing was blocked before it started
"Your current role does not have enough permissions to publish this project" Only Owners, Admins and Designers can publish. Ask for the Designer or Admin role. See What can each role do?.
The Publish tab is greyed out The project is read-only for you: your role can only view it, or the workspace's trial or subscription has ended. See Why can't I edit my project?.
A window titled "Upgrade workspace" opens when you click Publish The workspace has no active trial or plan. Choose a plan in the window, or close it with its ×: the Publish window then opens. See How to subscribe to Pro or Premium.
"Your project is still generating. Please wait for it to finish before publishing." Wait for the AI to finish building the project, then publish.
"Resolve the critical security violations before publishing." A workflow has a serious security problem. The Security warnings window opens: fix the issues marked Blocks publish. See Why does my workflow show missing configuration or security warnings?.
A window titled "Publishing Blocked" "Your project cannot be published because 1 workflow node contains forbidden SQL operations that modify the database structure." Click Go back and fix: the workflow opens on the step with the red warning icon. Keep only SELECT, INSERT, UPDATE or DELETE in its query, and change your tables in Data Sources instead.
"The maximum number of forms has been exceeded. Please upgrade your plan or delete some forms." The project has more forms that save submissions than your plan allows. Delete forms you don't use, or get more. See How many forms and submissions can I have?.
Language and web app limits
"Publishing failed: you have more languages in this project than active subscription slots. Purchase an extra language slot or remove a language from the project to continue publishing." Each language after the main one needs a language slot. Buy a slot, or remove a language. Language slots can't be bought during a trial. See How to buy extra language slots.
"Publish blocked: the following language subscriptions have expired: … Please renew them or remove these languages from the project." Renew the listed language slots, or remove those languages. See How to change the main language or remove a language.
"Publishing is blocked: this web app is over your team’s Web App quota. Buy a Web App slot to publish and run it." The project is a web app that isn't covered by a Web App slot, and its 7-day window is over. A window to subscribe the project opens: buy or assign a slot. See How to buy, assign or cancel a web app slot.
Other messages
"Error occurred while publishing" with a "Publish without private files" button The project has files in the Private folder that couldn't be published. Click Publish without private files to publish the site without them, or check those files. The status then reads Published (without private files). See What are the Private and Functions folders?.
"Staging environments are available on paid plans. Upgrade to test your changes on a private URL before they go live." The workspace has no active trial or plan. Publish to Production instead, or subscribe. See How to test changes on a staging site before going live.
"The staging build could not be kept separate from your live site, so it was cancelled. Your live site was not changed — please try again or contact support." Publish to Staging again. If it keeps happening, write to hello@teleporthq.io.
"Publishing to a custom Vercel account is no longer available for this project. Please publish via TeleportHQ hosting." Publish on TeleportHQ instead. See How to publish with your own Vercel account.
"An error occurred while publishing your application. Please try again. If the error persists, contact our support team. Error message: …" Wait a minute and publish again. If it fails again, write to hello@teleporthq.io and include the error message. See How to get help.
"Publishing failed. The site could not be password-protected, so this publish was discarded. Try again or contact support." In a workspace without a paid subscription, such as a trial, every publish puts the site behind a password. This time TeleportHQ couldn't add the password, so it discarded the publish: nothing new went live, and your site stays as it was. Publish again in a minute. If it happens again, write to hello@teleporthq.io. See Why does my published site ask for a password?.
Custom domain errors If publishing works but your domain can't be added or verified, see Why is my custom domain not working?.
Good to know
- Missing settings and broken links don't block publishing. The yellow issues chip at the top left of the editor lists them. The parts that need them, such as a workflow that sends email or a link to a deleted page, won't work on your live site until you fix them. See How to find and fix broken links on your site.
- Pages that failed to generate are left out of the published site, with the message "1 page that failed to generate was excluded from the published site." See Why don't my changes show on my live site?.