---
title: "corestack_site_copy_hold_set"
url: https://docs.corefinity.com/mcp/tools/corestack_site_copy_hold_set
type: tool
last_updated: 2026-11-13
feature: migrate
related:
  - https://docs.corefinity.com/guides/migrate/migrate-wordpress.md
---
# corestack_site_copy_hold_set

**Hold or release a copy.** Hold or release a target row while you copy a site into it. consumers: true stops the queue workers and the scheduled tasks starting anything (work the copy queues itself waits too) and completes only once the running work has finished; web: true answers "temporarily unavailable" (503) to every visitor, Corefinity's office included, and completes only once no request is in flight. WP-CLI, bin/magento, artisan, bin/console and your commands keep working. Hold consumers from before the first import until the cutover, and web around every import. A hold stays until you release it with false, or the person releases it from the dashboard: nothing else releases it. If the work does not finish in time the task fails and the hold stays on. Scope: write. Long-running: answers with a task.

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

## When to use it

Hold or release a target row while you copy a site into it. consumers: true stops the queue workers and the scheduled tasks starting anything (work the copy queues itself waits too) and completes only once the running work has finished; web: true answers "temporarily unavailable" (503) to every visitor, Corefinity's office included, and completes only once no request is in flight. WP-CLI, bin/magento, artisan, bin/console and your commands keep working. Hold consumers from before the first import until the cutover, and web around every import. A hold stays until you release it with false, or the person releases it from the dashboard: nothing else releases it. If the work does not finish in time the task fails and the hold stays on. The finished task's `web_drain` says how a web hold was proven: `fpm_nginx` means php-fpm and nginx were both seen quiet (Laravel, Magento 2 and Shopware, and WordPress on PHP 8.0 or later where its runtime has the php-fpm status listener); `nginx` means nginx was seen quiet and the site's longest allowed request time had passed, so it takes longer.

## Inputs

- `site_id` (integer, ≥ 1, required)
- `consumers` (boolean): true holds the queue workers and scheduled tasks, false releases them; leave out to keep as it is.
- `web` (boolean): true answers 503 to every visitor, false releases it; leave out to keep as it is.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "consumers": {
      "description": "true holds the queue workers and scheduled tasks, false releases them; leave out to keep as it is.",
      "type": "boolean"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    },
    "web": {
      "description": "true answers 503 to every visitor, false releases it; leave out to keep as it is.",
      "type": "boolean"
    }
  },
  "required": [
    "site_id"
  ],
  "type": "object"
}
```

## Refusals

- `switched_off`: the `exec` or `delete` kill switch is off; stop; tell the person.
- `runtime_not_adopted`: the copy hold's two barriers ship in the runtime component, and this row is not adopted yet; nothing was signed. A new target is born adopted; adopt the row with `corestack_runtime_adopt`, then hold.
- `busy`: another change is running on this row; wait for it (corestack_site_operation_get) and call again.
- `conflict`: `consumers: false` on the new environment of a move that has not gone live yet; its queue workers and scheduled tasks stay paused until the move goes live, which releases them; nothing was changed. Do not retry; tell the person.
- `work_failed`: the task's operation or deployment ended failed; `details` carries the record; read `details`; the person may retry with `corestack_operation_retry` where it applies.
- `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_site_copy_hold_set",
  "arguments": {
    "site_id": 4211,
    "consumers": true,
    "web": true
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_site_copy_hold_set with site_id 4211, consumers true, web true. (Hold or release a copy.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [Migrate WordPress](https://docs.corefinity.com/guides/migrate/migrate-wordpress.md)
