Skip to content
← All guides

Devora Cloud · Blog

What to read when the build fails

Devora Cloud · Reviewed on

A failed build does not replace the site already online. The AI reads the log, fixes the port, start or dependency and tries again.

Your AI chatDeploy my app on Devoradc_live_••••••••Reading devoracloud.com/llms.txt…POST /v1/projectsPOST /v1/databasesPOST /v1/deploymentsstatus: READYProject createdlojaPostgreSQL readyDATABASE_URLPrivate S3 createdS3_BUCKETZIP uploaded and builtREADYLive · HTTPShttps://loja.apps.devoracloud.com
Technical illustration. Features and regions depend on the plan, availability and application compatibility.

The first publish can fail on a detail: the start script, the port, a dependency that existed only on your machine. The Devora log shows the stage.

Open Logs in the project. Or ask the AI that published, if the token is still valid. It reads the diagnosis and tries again.

What not to do

Do not delete the project on the first error. Do not paste the whole log, with a secret, into a public chat. If the log showed the token or a password, revoke it and rotate the password.

What the live version does

While the new build fails, the ready version keeps answering. Only a publish that finishes replaces the previous one.

Frequently asked questions

Can the AI see the log without me copying it?

Yes, with the AI token still active. Without a valid token, it only reads what you paste.

What to read when the build fails · Devora Cloud