---
title: "corestack_enterprise_copy_resync"
url: https://docs.corefinity.com/mcp/tools/corestack_enterprise_copy_resync
type: tool
last_updated: 2026-11-13
feature: enterprise-copies
related:
  - https://docs.corefinity.com/guides/corestack-enterprise/websites-and-environments.md
---
# corestack_enterprise_copy_resync

**Re-sync a CoreStack Enterprise copy.** Copy a CoreStack Enterprise environment into the same CoreCluster site again, replacing what the last copy left there. Scope: write. Long-running: answers with a task.

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

## When to use it

Copy the same CoreStack Enterprise environment into the same CoreCluster site again, for example just before testing the
site with fresher data. A re-sync is a new copy that names the one it follows (`copy_of`); the one it follows, if not
finished, ends as superseded. Only the site's latest copy can be re-synced, once its run has ended, and the site is
judged again as for a first copy, including whose site it is now. It replaces everything the site holds, so type the
site's name as `confirm_target_site` only once the person has agreed.

The re-sync runs as a task; follow it with `corestack_enterprise_copy_get`. The public API's
`POST /api/enterprise-copies/{copy}/resync` does the same.

## Inputs

- `copy_id` (integer, 1 to 2147483647, required): the site's latest copy.
- `confirm_target_site` (string, required): the site's name, as the preview's `confirm`.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "confirm_target_site": {
      "description": "The site's name, typed once the person agreed.",
      "maxLength": 253,
      "type": "string"
    },
    "copy_id": {
      "maximum": 2147483647,
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "copy_id",
    "confirm_target_site"
  ],
  "type": "object"
}
```

## Refusals

- `copy_not_latest`: a newer copy of this site exists; re-sync that one. `copy_running`: the copy's run has not ended.
- The site's and the environment's checks, as a create's: `other_company`, `target_not_ready`, `target_live`,
  `target_sends_mail`, `target_unprotected`, `target_crons_on`, `target_busy`, `target_moving`, `source_moving`,
  `target_too_small`, `source_unsupported`, `ssh_unreachable`, …
- `confirm_mismatch` (field `confirm_target_site`): the name typed is not the site's.
- `managed_elsewhere`: the site is managed by another control panel.
- `tenant_mismatch`: the copy does not exist, its environment was deleted, or its environment or its site is not yours.
- `pin_refused` (`company_write`), `rate_limited` (5 copy changes a minute, shared with the public API), and the refusals
  every tool can answer: `scope_required`, `invalid_arguments`, `temporarily_unavailable`, `internal_error`
  (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_enterprise_copy_resync",
  "arguments": {
    "copy_id": 41,
    "confirm_target_site": "c32-s217"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_enterprise_copy_resync with copy_id 41. (Re-sync a CoreStack Enterprise copy.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [Websites and environments](https://docs.corefinity.com/guides/corestack-enterprise/websites-and-environments.md)
