---
title: "Build Logs"
description: "Follow a Testing build, inspect an earlier deploy, and locate source errors in build output."
permalink: /docs/oxide/debugging/build-logs/
---
# Build Logs

Build logs show the operations that process your project's backend, app, and CloudCode source during a deploy. Use them when a deploy fails or when you need to identify which build step produced an error.

A CloudCode task's execution output is separate from its build output. For an invocation that fails after deployment, use [CloudCode testing and logs](/docs/oxide/cloudcode/testing-and-logs/).

## Follow a Testing Build

Open the **Live build logs** panel from the command palette. It follows the most recent deploy for your active [Testing deployment](/docs/oxide/testing-and-releases/configuring-testing-deployments/), including output arriving while the build runs.

To open this panel automatically, find these settings under **Editing**:

| Setting | Behavior |
| --- | --- |
| **Show output when build fails** | Opens live output when a build on the active Testing target fails. Enabled by default. |
| **Show output when build starts** | Opens live output as soon as a build starts on the active Testing target. Disabled by default. |

These settings follow the active Testing target. Use a deployment's history to inspect a different target or an earlier release. For finding panels and settings, see [Workspaces and actions](/docs/guides/workspaces-and-actions/).

## Inspect an Earlier Build

1. Open **Deployments**, expand the intended deployment, and open its **Deploy logs** section.
2. Select the deploy event matching the time and source version you are investigating.
3. Expand the event to see its build-operation buttons.
4. Select an operation to open the build-output panel for that deploy.
5. Inspect the failed operation and the messages leading up to its error.

The panel groups output by operation and displays its status, duration, and log levels. **No output** means that operation has no recorded messages; check its status and the other operations before deciding that the overall deploy succeeded.

## Locate a Source Error

Where output contains a recognized file path and line/column location, OXIDE turns it into a source link. Select the link to open the relevant code, including source in an app package or a library within a TypeScript project when the file can be resolved.

Check the reported build's source version before editing. An older build may refer to a file or line that has since changed in your active draft.

For tests run during an [app-package build](/docs/runtime/app-packages/app-packages-overview/), the operation output also contains the test runner's report. ANSI formatting is retained so that errors and test results remain readable.

## Verify the Fix

Correct the source or configuration identified by the failed operation, then repeat the intended deploy and check its result. Use [App Settings](/docs/oxide/testing-and-releases/app-settings/) for project build/runtime configuration and [Release an app](/docs/oxide/testing-and-releases/release/) for target selection and release checks.

A successful build confirms that source was processed. Use [app diagnostics](/docs/oxide/debugging/app-diagnostics-reports/) when the remaining problem occurs on a device after the release.