# How do I investigate a failed Run deployment?

Company: Socra — Multiply Your Judgment
Canonical URL: https://support.socra.com/articles/art_01m46fsrzfb7bj4dvw9cd3cp8p-troubleshoot-a-run-deployment

Inspect the specific Deployment's status, logs, and lifecycle events before starting another attempt. The Workload identifies the application, while the Deployment ID identifies the attempt that failed. Keeping that distinction lets you inspect the error without confusing it with a later release.

## Find the attempt

Use the Socra CLI with the Account and Run plugins, signed in to the Account that owns the Project. If you have the `dpl_…` ID from the deployment response, use it directly. Otherwise replace `PROJECT_ID` with the Project's ID and list its deployments:

```sh
socra run deployment list --project PROJECT_ID
```

The list supports `--limit` and `--after`. Follow its continuation cursor when more results remain. Check the Workload and timestamps before choosing the Deployment to inspect.

## Read the evidence

Replace `DEPLOYMENT_ID` with the selected `dpl_…` ID:

```sh
socra run deployment get DEPLOYMENT_ID
socra run status DEPLOYMENT_ID
socra run logs DEPLOYMENT_ID
socra run events DEPLOYMENT_ID
```

The deployment record identifies the image, configuration, status, and error. Status reports health and any URL. Logs show runtime output, and events show lifecycle progress.

Use the first specific error to choose the next check. Confirm that Run can pull the pinned image, that the configured runtime settings match the application, and that required Project-owned Secrets are accessible. A permission or disabled-service error needs an access or enablement correction before another deployment attempt.

A job has no service URL. That absence alone does not indicate failure. For a service Workload, inspect its health and URL separately from custom-domain routing.

## Recheck before retrying

A lost terminal connection does not establish that the Deployment stopped. Retrieve the Deployment again and inspect its durable state before issuing another deployment command.

If you need to return to an earlier successful configuration, Run supports rollback to an immutable Revision. First inspect the intended Revision:

```sh
socra run revision get REVISION_ID
```

Replace `REVISION_ID` with the `rev_…` ID of the known successful Revision. Rollback creates another deployment attempt from that Revision. It does not undo data changes made by your application.

The [Run CLI reference](https://cloud.socra.com/docs/run/reference/cli) contains the rollback and deployment controls. Preserve the failing Deployment ID and the relevant error when you ask a Project administrator for help.

## Article details

- Collection: [Cloud](https://support.socra.com/collections/col_01kzpmz634mj0yhn7efqjkem66-cloud)
- Canonical: https://support.socra.com/articles/art_01m46fsrzfb7bj4dvw9cd3cp8p-troubleshoot-a-run-deployment