Skip to main content
Every time your site is deployed, Hiveku writes down each step: preparing your files, building, putting it live. When a deploy fails, it says which step stopped and why. Once the site is live, its server writes lines of its own as visitors come in. Both are on your site’s Hosting page. This guide reads the logs of Northwind’s Pearl District test site: one deploy that worked, one that failed, and the lines the site wrote while serving visits.

​
Open Hosting

1

Open the site's Hosting page

Click Websites in the left rail. On the site’s card, click the ⋮ at the top right, then Hosting.
2

Pick an environment

Click Development, Staging or Production at the top. Each one keeps its own deploys and logs.
Hosting and Infrastructure for Northwind Pearl District, with the tabs Live Preview, Development, chosen, Staging, Disabled, and Production, outlined

The environments, at the top of Hosting

​
Read a deploy’s log

Scroll to Deployment History and open Recent Deployments. Each deploy shows whether it Succeeded or Failed, when it started and how long it took. Click View Full Build Logs to see every step, each at the time it happened.
A Succeeded Development deploy from 10/22/2026 at 8:12 PM, 199.7 seconds, with Succeeded and View Full Build Logs outlined, and its log: Started the Development deploy, Preparing your 62 files, Building your site, Installing your site's packages, Building your pages, Built your site in 87s, the install step, Putting your site live, The new version passed Hiveku's check, Your site's address is ready, and Done in 197.0s

A deploy that worked, step by step

The lines under Install step are your site’s package installer at work, as it printed them. Green lines are the milestones: built, checked, live.

​
Find out why a deploy failed

A failed deploy opens with a Build Error box. Its first lines say which step stopped and the first real error. When the problem is on Hiveku’s side, the box says your code is not the cause.
A Failed Development deploy from 10/22/2026 at 7:50 PM, with Failed outlined, and the Build Error, outlined: The build failed after 98s. Building your site stopped. The Development deploy failed: components/sections/index.ts: Cannot find module ./hero/full-bleed-image-hero

A deploy that failed, and why

Here a section of the site pointed to a file that wasn’t there. Ask the builder AI to fix it and paste the error in your message, then deploy again. A failed deploy changes nothing: visitors keep seeing the last version that worked.

​
Read what your site printed

Further down, under Analytics & Monitoring, Runtime logs lists what your site’s server wrote in the last 60 minutes: when it started, and any errors while it handled a page or a form. Click Refresh for newer lines.
Runtime logs, Development environment, Kept for 30 days, Last 60 minutes, with Refresh outlined and Show system lines (52) outlined, and the lines the site's server wrote as it started, colored by Info/Success, Warning and Error

Runtime logs for Development

Lines are colored: green for information, yellow for warnings, red for errors. They are kept for 30 days.

​
Good to know

  • No lines yet? Lines appear when your site gets visits. A site made only of static pages writes none.
  • Try a fix on a branch first. A deploy from a branch to Development leaves your live site alone: see Try a Change on a Branch First.
  • Publishing: see Publish Your Changes.