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

**Pipeline rehearsal.** A deployment pipeline rehearsal's state and result: each step's outcome, where and why a failed one stopped (redacted), and the lines it skipped. Also reads the rehearsal of a move from CoreStack Enterprise onto this environment. Scope: read.

- Scope: `read`
- Runs as a task: no

## When to use it

Read a pipeline rehearsal: its state (`running`, `passed`, `failed`), the result panel's five steps (`build`, `upload`, `shared_files`, `platform_step`, `database` — each `pending`, `running`, `passed`, `failed` or `skipped`), a failed one's `failure` (`step`, `task`, `message`, redacted) and `failed_line` when a database line stopped it, and the lines it skipped because they reach third parties. `rehearsal_id` comes from `corestack_deployments_rehearse`, or from the carried-over pipeline's rehearsal (`corestack_deployments_carryover_get`) for an environment moved from CoreStack Enterprise, which it reads too.

The same action in the public REST API, with the same checks, refusals and scope: `GET /api/corestack/sites/{site}/deployments/rehearsals/{rehearsal}`.

## Inputs

- `site_id` (integer, ≥ 1, required)
- `rehearsal_id` (integer, ≥ 1, required): From corestack_deployments_rehearse, or the carried-over pipeline's rehearsal.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "rehearsal_id": {
      "description": "From corestack_deployments_rehearse, or the carried-over pipeline's rehearsal.",
      "minimum": 1,
      "type": "integer"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id",
    "rehearsal_id"
  ],
  "type": "object"
}
```

## Refusals

- 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_rehearsal_get",
  "arguments": {
    "site_id": 4212,
    "rehearsal_id": 37
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_deployments_rehearsal_get with site_id 4212, rehearsal_id 37. (Pipeline rehearsal.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/sites/{site}/deployments/rehearsals/{rehearsal}](https://docs.corefinity.com/api/reference/deployments/get-site-deployment-rehearsal.md)
- Guide: [Pipeline](https://docs.corefinity.com/guides/sites/code-and-deployments/pipeline-stages.md)
