---
title: "corestack_deployments_carryover_accept"
url: https://docs.corefinity.com/mcp/tools/corestack_deployments_carryover_accept
type: tool
last_updated: 2026-11-13
feature: deployment-pipeline
related:
  - https://docs.corefinity.com/api/reference/deployments/accept-site-deployment-carried-over.md
  - https://docs.corefinity.com/guides/sites/code-and-deployments/pipeline-stages.md
---
# corestack_deployments_carryover_accept

**Accept the carried-over pipeline.** Decide the carried-over pipeline lines waiting for review — accept, remove, or edit each, by the stage and index corestack_deployments_carryover_get gives — so the binding can deploy again. Scope: write. Also needs exec when the deployment pipeline gains a custom line.

- Scope: `write`
- Also needs `exec` when an `edit` action with new text
- Runs as a task: no

## When to use it

Decide the carried-over lines waiting for review on one binding: `accept`, `remove`, or `edit` with one new line of text, each by the `source` stage and index `corestack_deployments_carryover_get` gives, with the binding's `revision` from it. Once no line is left in review the binding deploys again. Send `lines: []` to accept a translation with nothing in review. An edit with text the stage does not run now also needs exec.

The same action in the public REST API, with the same checks, refusals and scope: `POST /api/corestack/sites/{site}/deployments/carried-over/accept`.

## Inputs

- `site_id` (integer, ≥ 1, required)
- `binding_id` (integer, ≥ 1, required)
- `lines` (array of {stage, index, action, text?}, at most 600 items, required)
- `revision` (string): The binding's revision from corestack_deployments_carryover_get; leave it out while that is null (a binding still classic).

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "binding_id": {
      "minimum": 1,
      "type": "integer"
    },
    "lines": {
      "items": {
        "additionalProperties": false,
        "properties": {
          "action": {
            "enum": [
              "accept",
              "remove",
              "edit"
            ],
            "type": "string"
          },
          "index": {
            "minimum": 0,
            "type": "integer"
          },
          "stage": {
            "enum": [
              "build",
              "database",
              "post_deploy"
            ],
            "type": "string"
          },
          "text": {
            "description": "With edit: the new line.",
            "maxLength": 4096,
            "type": "string"
          }
        },
        "required": [
          "stage",
          "index",
          "action"
        ],
        "type": "object"
      },
      "maxItems": 600,
      "type": "array"
    },
    "revision": {
      "description": "The binding's revision from corestack_deployments_carryover_get; leave it out while that is null (a binding still classic).",
      "type": "string"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id",
    "binding_id",
    "lines"
  ],
  "type": "object"
}
```

## Refusals

- `forbidden`: the person's role lacks the Edit Environment Deployment Pipeline permission. The message names it and
  says an owner of the company can grant it in Roles; `details.permission` is `editEnvironmentDeploymentPipeline`.
  Nothing is changed.
- `stale`: the translation or the pipeline changed since you read it; read it again and decide again.
- `not_available`: nothing was carried into this binding.
- `variable_invalid`: a credential the carry moves into a variable cannot be stored; contact support.
- `invalid_arguments` on `lines.<n>` with "This line still runs n98-magerun, which CoreStack does not have…": you accepted a line that still calls `n98` (or `magerun2`, `n98-magerun2`) as it is, or edited a line into one that does. A line that only names it as a word (an `echo`, a here-string) counts too: reword it. CoreStack has no n98-magerun, so the deployment would fail on it. Edit the line to run its Magento commands as `php bin/magento` instead (`php bin/magento cache:flush` for `n98 cache:flush`), or remove it. The line's `reason` in `corestack_deployments_carryover_get` says the same.
- `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_deployments_carryover_accept",
  "arguments": {
    "site_id": 4211,
    "binding_id": 812,
    "lines": [
      {
        "stage": "build",
        "index": 3,
        "action": "remove"
      }
    ],
    "revision": "r-8f2c"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_deployments_carryover_accept with site_id 4211, binding_id 812, lines [{"stage":"build","index":3,"action":"remove"}], revision r-8f2c. (Accept the carried-over pipeline.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [POST /api/corestack/sites/{site}/deployments/carried-over/accept](https://docs.corefinity.com/api/reference/deployments/accept-site-deployment-carried-over.md)
- Guide: [Pipeline](https://docs.corefinity.com/guides/sites/code-and-deployments/pipeline-stages.md)
