---
title: "corestack_enterprise_deployment_retry"
url: https://docs.corefinity.com/mcp/tools/corestack_enterprise_deployment_retry
type: tool
last_updated: 2026-11-13
feature: enterprise-deployments
related:
  - https://docs.corefinity.com/guides/corestack-enterprise/deployments-and-pipelines.md
---
# corestack_enterprise_deployment_retry

**Retry a CoreStack Enterprise deployment.** Run a CoreStack Enterprise deployment again, built from its pipeline as it is now, or from the step that failed. Scope: write. Long-running: answers with a task.

- Scope: `write`
- Runs as a task: yes

## When to use it

Run a CoreStack Enterprise deployment again, as the same row, built from its pipeline as it is now: the list's and the
page's Retry. Usually for a failed or cancelled deployment, or to deploy the live release again.

With `from: failed_step` it is the page's "Retry from the failed step" instead: a failed deployment carries on from the
step that failed, in the same release, and no step that finished runs again. Only where the page offers it: read the
deployment with `corestack_enterprise_deployment_get` first, and send `failed_step` only when its `view.actions` lists
`retry_from_step`. Anywhere else the tool refuses `retry_from_step_unavailable` and nothing starts; retry from the start
instead (leave `from` out).

Retrying a deployment that is not the environment's newest puts its older commit live over the newer one. The tool
refuses it with `confirm` and a message naming both deployments. Show the person that message, and only once they
agree, call again with `confirm_older: true`. Retrying the newest deployment needs no confirmation.

A task follows the deployment to its end. The public API's
`POST /api/environments/{environment}/deployments/{deployment}/retry` answers the same, with the same `confirm_older`
and `from`.

## Inputs

- `enterprise_env_id` (integer, ≥ 1, required)
- `deployment_id` (integer, ≥ 1, required)
- `confirm_older` (boolean): required, as true, to retry a deployment that is not the environment's newest
- `from` (`start` or `failed_step`, default `start`): where the retry starts. `start` runs the whole pipeline again;
  `failed_step` carries on from the step that failed, where the deployment's page offers it

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "confirm_older": {
      "type": "boolean"
    },
    "deployment_id": {
      "minimum": 1,
      "type": "integer"
    },
    "enterprise_env_id": {
      "description": "A CoreStack Enterprise environment's id; for CoreStack or CoreCluster use the corestack_deployment_* tools.",
      "minimum": 1,
      "type": "integer"
    },
    "from": {
      "default": "start",
      "enum": [
        "start",
        "failed_step"
      ],
      "type": "string"
    }
  },
  "required": [
    "enterprise_env_id",
    "deployment_id"
  ],
  "type": "object"
}
```

## Refusals

- `retry_from_step_unavailable` (field `from`): "Retry from the failed step is not available for this deployment, so
  retry it from the start instead." The page does not offer it for this deployment (it has not failed, the step that
  failed cannot be run again on its own, something it depends on changed since, or it is not available on this
  environment). Call again without `from`.
- `confirm` (field `confirm_older`): this is not the environment's newest deployment, so retrying it puts an older
  release live. The message names the commit and date of both; ask the person before you send `confirm_older: true`.
- `stale`: the deployment moved on, or cannot be retried in its current state (a legacy scheduled deployment can only
  be cancelled). Read it again.
- `artifact_pruned`: this deployment's archive was removed after 30 days, so it can't be retried. Deploy again from the
  commit (`corestack_enterprise_deployment_trigger`). Archives are kept for 30 days, and always for an environment's 10
  most recent deployments and its newest successful one.
- `busy`: the same retry is still being applied. `forbidden`: the person's role lacks the Retry Deployments permission
  (a retry from the failed step asks the same). The message names it and says an owner of the company can grant it in
  Roles; `details.permission` is `retryDeployments`.
- `invalid_arguments`: on `enterprise_env_id`, a CoreStack or CoreCluster environment (use `corestack_deployment_retry`
  by `site_id`); on `from`, anything but `start` or `failed_step`.
- `tenant_mismatch`, `pin_refused`, and the refusals every tool can answer: `scope_required`, `rate_limited`,
  `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_enterprise_deployment_retry",
  "arguments": {
    "enterprise_env_id": 1530,
    "deployment_id": 185172
  }
}
```

Once the person has agreed to put the older release live:

```json
{
  "name": "corestack_enterprise_deployment_retry",
  "arguments": {
    "enterprise_env_id": 1530,
    "deployment_id": 185160,
    "confirm_older": true
  }
}
```

From the step that failed, once `corestack_enterprise_deployment_get` lists `retry_from_step` in `view.actions`:

```json
{
  "name": "corestack_enterprise_deployment_retry",
  "arguments": {
    "enterprise_env_id": 1530,
    "deployment_id": 185172,
    "from": "failed_step"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_enterprise_deployment_retry with enterprise_env_id 1530, deployment_id 185172. (Retry a CoreStack Enterprise deployment.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [Deployments and pipelines](https://docs.corefinity.com/guides/corestack-enterprise/deployments-and-pipelines.md)
