UlikaDocs
Open Ulika

Getting started

  • Ulika documentation
  • How Ulika works
  • Requirements
  • Quickstart

Connect a site

  • Connect from the dashboard
  • Connect with the CLI
  • Connect with an AI agent
  • Approving a connection
  • Private previews
  • The GitHub App
  • Connect Vercel

Integrations

  • GitHub integration
  • Vercel integration
  • Netlify
  • Claude Code
  • Codex
  • MCP tools

Editing

  • The editor
  • The style panel
  • Sections and pages
  • Mobile preview, autosave and drafts

Publishing

  • Publish your changes
  • History and restoring a version
  • When a publish fails

Team

  • Team roles
  • Inviting people

Projects

  • Project settings
  • Delete a project
  • Website code

Troubleshooting

  • Needs attention reasons
  • Vercel problems
  • GitHub problems
  • CLI errors and exit codes
  • Frequently asked questions

Security and privacy

  • Security and privacy overview

CLI

  • CLI reference
  • CLI changelog

Publishing

When a publish fails

What Ulika does when a publish does not reach your live site, the exact messages you may see, who is told, and how to fix or retry without losing drafts.

Last updated October 10, 2026

A publish can stop before your live site shows the new version: the host's build fails, the connection to GitHub is broken, or Ulika cannot confirm the new version after waiting. In every case your drafts stay saved, and Ulika only counts a publish as done when your live site proves it serves the new content.

The short version#

  1. Your drafts are never thrown away by a failed publish.

  2. A failed publish does not appear in History. Only a publish proven live does.

  3. Fix the cause, then open Publish and publish again.

Who is notified#

Verified in the product code: Ulika does not send an email, a Slack message or any other notification when a content publish fails. The failure is shown:

  • To the person who clicked Publish, if the dialog is still open or they open it again: as a notice in the dialog and a toast, "Publication not confirmed" (or "Publish failed" when the request itself was refused).

  • Nowhere else. A teammate who did not start the publish will not hear about it.

So if you start a publish and close the tab, come back and check History: if your change is not at the top with the Live now badge, open Publish and click the publish button again. Ulika resumes the same saved publish, or starts a fresh one if you have changed anything since.

Tip

After a publish you care about, open the live page and confirm the change is there. That is the only check that does not depend on Ulika.

What happens to the live site#

Visitors keep seeing the last version that was proven live. If Ulika had already shown your change early (see How fast visitors see it) and the deployment is then confirmed failed or canceled, Ulika stops serving the early values and visitors go back to the previous version.

Whether your host keeps the previous deployment online when a build fails is up to the host. Ulika does not control it, and none of the messages below promise it for a content publish. The one place Ulika states it is for a failed connector install, covered next.

Messages and what to do#

These are the exact texts Ulika uses. "Your drafts are saved" in each message is true.

Vercel confirmed that the deployment failed or was canceled#

Vercel confirmed that the deployment failed or was canceled. Your drafts are saved; correct the content and publish again.

Cause: Vercel itself reported a failed or canceled build for the deployment your publish started. Ulika only declares a failure after receiving that signed message from Vercel; it never guesses from waiting time.

Fix:

  1. Open your project on Vercel, go to Deployments and open the failed one to read the build log.

  2. If the failure is in your code or settings (a changed build command, a missing environment variable), fix that on your side.

  3. If a content value broke the build, undo it in the editor and publish again.

  4. Publish again.

The deployment is not confirmed live yet#

The deployment is not confirmed live yet. Reopen Publish to retry the same saved release.

Cause: more than 15 minutes passed after Ulika sent the publish and your live site still does not serve it, but no failure was reported either. It can be a very slow build, a build still queued, or a site whose address Ulika cannot read.

Fix: reopen Publish. Ulika retries the same saved publish. If it keeps happening, open your host's deployment list to see what happened, and check Troubleshooting Vercel.

Publication is still being checked#

Publication is still being checked. Reopen Publish to resume checking.

Cause: the Publish dialog watches for up to 15 minutes. This is only the dialog giving up, not a failure. The publish itself is still tracked in the background.

Fix: reopen Publish to resume checking, or just wait and look at the live site.

Could not check publication#

Could not check publication. Your drafts remain saved; reopen Publish to check again.

Cause: the status check itself failed, for example because your internet connection dropped. The publish may be fine.

Fix: reload, reopen Publish, and it checks again.

Vercel returned an error code or did not confirm the request#

Vercel returned 500. Publication is unconfirmed; drafts remain saved. Retry after 15 minutes.

Vercel did not confirm the request. Publication is still being checked; drafts remain saved. Retry after 15 minutes.

Cause (project connected through a Vercel deploy hook): Ulika asked Vercel to rebuild and either got an error status (the number varies) or no answer in 20 seconds. A build may still have started. Ulika keeps the saved publish pending until your real site proves what was deployed.

Fix: wait a little, check the live site and your Vercel deployments, and retry after about 15 minutes if nothing happened. If the deploy hook was deleted or changed, reconnect Vercel (see Troubleshooting Vercel).

The repository received several commits while publishing#

The repository received several commits while publishing, so nothing was published yet. Publish again in a moment; drafts remain saved.

Cause (project connected through GitHub): Ulika writes .ulika/content.json with a safe, conditional update. Other pushes landed at the same time, so Ulika backed off.

Fix: publish again in a moment.

The site's GitHub repository is not connected#

This site's GitHub repository is not connected to Ulika, so the publication could not be sent. Reconnect the repository, then publish again.

Cause: Ulika lost the link to the repository, for example because the GitHub App was uninstalled or access was removed.

Fix: reconnect the repository (see Troubleshooting GitHub and Change the repository), then publish again.

needs-merge and content-file-changed#

These two are not failures, they are decisions. Ulika waits for you.

  • Waiting for the pull request to be merged: your branch is protected. Merge the pull request that Ulika opened. See Publish your changes.

  • Your repository's .ulika/content.json was changed outside Ulika: choose Overwrite with Ulika's version or inspect the commit first. See Publish your changes.

A publish replaced by a newer one#

If you press Publish again after saving more edits while the first publish was still building, the first is closed and the new one carries everything. This is intentional, so nothing you edited is left out. It is not an error, and you do not need to do anything.

A failed build right after connecting#

A different case: you approved Ulika's connector pull request, Ulika merged it, and your host's production build then failed. Ulika handles that itself and tells you in the project:

Your host's production build failed after Ulika merged the connector, so Ulika reverted its own change. Your live site kept serving the previous deployment. Check the build log on your host, then create a new connector pull request.

or, when it could not revert:

Your host reports that the production build failed after the connector was merged. Your live site keeps serving the previous deployment. Open the build log on your host to see why.

When a revert needs a human (for example your branch rules require a review), Ulika opens a revert pull request instead and waits for you to merge it. See Connect approval and Connect and approval problems.

Role requirements#

Only people who can publish (owners and editors) can retry a publish or use Overwrite with Ulika's version. See Roles.

Was this page helpful?

PreviousHistory and restoring a versionNext Team roles

On this page

  • The short version
  • Who is notified
  • What happens to the live site
  • Messages and what to do
  • Vercel confirmed that the deployment failed or was canceled
  • The deployment is not confirmed live yet
  • Publication is still being checked
  • Could not check publication
  • Vercel returned an error code or did not confirm the request
  • The repository received several commits while publishing
  • The site's GitHub repository is not connected
  • needs-merge and content-file-changed
  • A publish replaced by a newer one
  • A failed build right after connecting
  • Role requirements
Ulika documentationFAQ · CLI reference · Terms · Privacy