---
title: "Deployment log"
url: https://docs.corefinity.com/guides/sites/code-and-deployments/deployment-log
type: guide
last_updated: 2026-11-13
feature: deployments
related:
  - https://docs.corefinity.com/api/reference/deployments/get-site-deployments.md
  - https://docs.corefinity.com/api/reference/deployments/create-site-deployment.md
  - https://docs.corefinity.com/api/reference/deployments/list-site-deployment-branches.md
  - https://docs.corefinity.com/api/reference/deployments/update-site-deployment-mode.md
  - https://docs.corefinity.com/api/reference/deployments/list-site-deployment-repositories.md
  - https://docs.corefinity.com/api/reference/deployments/update-site-deployment-repository.md
  - https://docs.corefinity.com/mcp/tools/corestack_deployments_get.md
  - https://docs.corefinity.com/mcp/tools/corestack_deployments_mode_set.md
  - https://docs.corefinity.com/mcp/tools/corestack_deployments_repositories_list.md
  - https://docs.corefinity.com/mcp/tools/corestack_deployments_branches_list.md
  - https://docs.corefinity.com/mcp/tools/corestack_deployments_repository_set.md
  - https://docs.corefinity.com/mcp/tools/corestack_deployment_trigger.md
---
# Deployment log

Open a deployment's page to follow it live, find the command that failed and copy its output.

## Before you start

- You can open the site in **Managed Websites**. Anyone who can open a site can read its deployment logs.
- The site has at least one deployment: see [Deploy, stop, retry and roll back](/guides/sites/code-and-deployments/deploy-stop-retry-roll-back).

## Find out why a deployment failed

1. **Open the deployment**

   Go to **Managed Websites**, choose the site, then **Deployments** under **Code & backups**, and choose **View log** on the deployment's row. The banner at the top says where it stopped, such as **Build failed on Production**.

   _Screenshot: The page of a failed deployment: the banner Build failed on Production with Go to failed task and Raise a ticket, the Job log with the failing build command open on its error lines, and the cards for status, timing, target, source and commit._

2. **Read the failing command**

   Choose **Go to failed task**. The **Job log** opens the command that failed, with its **Exit code** and its last lines of output.

3. **Copy or search the output**

   Choose **Copy output** to copy a task's output, or enter text in **Search log output** to find a line.

   _Screenshot: The Job log of a failed deployment with Unable to resolve entered in the search box, ringed, and the number of matches beside it. The Build task is open on its Exit code, Copy output and the one matching line, highlighted._

**Raise a ticket** opens a new support ticket with the deployment filled in. To build the same commit again, retry the deployment: see [Deploy, stop, retry and roll back](/guides/sites/code-and-deployments/deploy-stop-retry-roll-back).

## Read the log

The **Job log** groups a deployment's tasks in the order they run. Each group reads **passed**, **failed**, **running** or **queued**.

| Group                       | What happens                                                               |
| --------------------------- | -------------------------------------------------------------------------- |
| **Prepare and source**      | The repository is checked out and your build commands run.                 |
| **Release**                 | The release is uploaded and its shared files are linked.                   |
| **Database**                | Scheduled tasks and the queue are paused and your database commands run.   |
| **Switch and after deploy** | The site switches to the new release, then your after-deploy commands run. |

_Screenshot: The page of a deployment that succeeded: every group of the Job log marked passed and the Build task open on its commands and their output, beside the cards for status, timing, target, source, commit and recent deployments on Production._

The cards beside the log show the deployment's status and duration, its **Timing**, its **Target** environment, its **Source** repository and branch, and its **Commit**. A [variable](/guides/sites/code-and-deployments/variables-and-secrets) that is **Hidden** is masked in the log and in the stored output.

## Follow a running deployment

1. **Follow the log**

   Open the **Running** deployment and choose **Follow log**.

   _Screenshot: The page of a running deployment: the note Deployment in progress with Follow log, the Build task marked Running with its duration so far, and the Stop deployment button._

The log scrolls with the output as each task runs.

## Related

- [Deploy, stop, retry and roll back](/guides/sites/code-and-deployments/deploy-stop-retry-roll-back): Deploy, stop, retry or roll back.
- [Pipeline](/guides/sites/code-and-deployments/pipeline-stages): Change what a deployment runs.
- [Logs](/guides/sites/logs-and-monitoring/logs): Read and narrow a site's logs.
