---
title: "corestack_operation_retry"
url: https://docs.corefinity.com/mcp/tools/corestack_operation_retry
type: tool
last_updated: 2026-11-13
feature: operations
related:
  - https://docs.corefinity.com/api/reference/sites/retry-operation.md
  - https://docs.corefinity.com/api/long-running-work.md
---
# corestack_operation_retry

**Retry a failed change.** Retry a failed change the control panel lets you retry; the new attempt resumes from where the failed one stopped. Scope: write. Also needs destructive when it retries a site delete, an environment delete or a clone onto production. Long-running: answers with a task.

- Scope: `write`
- Also needs `destructive` when site delete, environment delete, clone onto production
- Runs as a task: yes

## When to use it

Retry a failed change the Control Panel lets you retry; the new attempt resumes from where the failed one stopped.

## Inputs

- `operation_id` (integer, ≥ 1, required): The failed operation (the latest of its row).
- `acknowledge_env` (boolean): Required true when the failure was env_drift: you have checked the live .env file and it is the one to continue from.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "acknowledge_env": {
      "description": "Required true when the failure was env_drift: you have checked the live .env file and it is the one to continue from.",
      "type": "boolean"
    },
    "operation_id": {
      "description": "The failed operation (the latest of its row).",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "operation_id"
  ],
  "type": "object"
}
```

## Refusals

- `not_retryable`: `corestack_operation_retry` on an operation that cannot be retried; stop.
- `stale`: a later change has overtaken this one, so retrying it would put the older change back; nothing was changed. A failed Attach domain after a newer attach of the same environment completed, or after its domains changed another way; a failed main-domain change after a later one, or once the site's addresses changed. Read the site's domains with corestack_domains_get and make a new change instead.
- `platform_plugins_off`: a failed Attach domain of a WordPress production site whose platform plugins have been turned off since; nothing was changed. Turn them back on with corestack_site_platform_plugins_set (`enabled: true`), wait for the task it answers to complete, then retry.
- `platform_plugins_applying`: the same, while the platform plugins are back on but the platform has not finished applying that; nothing was changed. Try again in a minute; if it stays, turn them on again with corestack_site_platform_plugins_set (`enabled: true`), wait for the task it answers to complete, then retry.
- `managed_elsewhere` (message: "This site is managed by another control panel"): another control panel manages this site, so use that control panel for it. This is refused before anything else about the site, as in the Control Panel and the API. Nothing was done.
- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_operation_retry",
  "arguments": {
    "operation_id": 77120
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_operation_retry with operation_id 77120. (Retry a failed change.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [POST /api/corestack/operations/{operation}/retry](https://docs.corefinity.com/api/reference/sites/retry-operation.md)
- Guide: [Long-running work](https://docs.corefinity.com/api/long-running-work.md)
