corestack_ deployments_ rehearsal_ get
Pipeline rehearsal.
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 /.
Ask for it
Using the Corefinity MCP server, call corestack_deployments_rehearsal_get with site_id 4212, rehearsal_id 37. (Pipeline rehearsal.) Tell me what it returned.Inputs
From corestack_deployments_rehearse, or the carried-over pipeline's rehearsal. At least 1.
At least 1.
Example call
{
"name": "corestack_deployments_rehearsal_get",
"arguments": {
"site_id": 4212,
"rehearsal_id": 37
}
}If it is refused
| Reason | What to do |
|---|---|
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |