Publish was blocked or failed

What you see: a red box in the Publish dialog with one of the sentences below, and Publish blocked. See why in the header afterwards.

In every case but two, nothing was published and your live site is exactly as it was. Each message carries the time it was raised, so an old one is not mistaken for a new one.

The security check

“One thing to check before going live.” Before every publish, Anela checks the site for problems that would expose you or your visitors. The message names what it found:

A key or password in the published files. Ask Anela AI to move it to the Secrets panel and remove it from the files.
Data that anyone could read. A table your site uses has no protection. Ask Anela AI to protect it so each visitor sees only their own rows.
A part of your site that hands out data without asking who is asking. If that is a mistake, ask Anela AI to add a check. If that part is meant to be public, tick the confirmation in the dialog, once, and publish again.

“We could not finish checking your site.” The check itself could not complete, often because the database did not answer in time. Wait a minute and publish again.

A database change that cannot go live

“Publish stopped by a database change.” A change in your preview cannot be copied to the live site as it is: for example a rule written in a way we cannot copy, or a database function that deletes entries without checking who is asking. It also stops when a change you asked for on your live site’s data no longer fits it, for example because a visitor already added the same entry. The message names the change. Nothing was applied and your live site is unchanged. Ask Anela AI to undo or adjust it, then publish again.

Publishing never removes your live site’s data unless you asked Anela AI for that change. If you remove a table or column in the preview that still holds data on the live site, publishing keeps it there.

The project or its database was not ready

“Your project could not be woken up.” The project went to sleep and did not wake in time. There is nothing to fix in your project: wait a moment and press the button again. Publishing wakes the project by itself, so there is no need to send a message.
“Your site is still getting set up.” A new project is still being prepared. Wait a minute.
“This copy is still being set up.” / “This copy is not ready to publish.” A duplicated project’s own database and files are still being prepared. Wait a minute.
“Your database did not answer.” Wait a moment and publish again. If it repeats, ask Anela AI to check the database from the Assets tab.
“The live site’s functions did not deploy.” Your pages built, but the copy of your server functions for the live site could not be deployed. The message says why; ask Anela AI to fix it, then publish again.

Something else was running

“Your site is still being worked on.” A build is running. Wait for it to finish, or press Stop, then publish.
“A publish is already running.” Wait for it to finish.
“The server is busy building other sites.” Try again in a minute.
“This publish took too long and was stopped.” Try again. If it keeps happening, ask Anela AI whether the site’s build has grown very large.

The publish itself failed

“We could not finish putting your site live.” Publish again.
“Your site changed, even though the publish failed.” The new version did reach your address, but the final record failed. Check the live site, then publish again so everything is in order.
“We could not confirm whether your site changed.” Check the live site. Publish again to be sure.

Still blocked

If the same message comes back after two tries, tell us through Report in the editor. Include the sentence you see.

Verified against the product on 2026-09-07.

Build your website with Anela at anela.ai