corestack_ deployment_ stop
Stop a deployment.
When to use it
Stop a deployment that is queued or running. Where Stop termination is enabled for the environment, a running step's
commands are ended on the servers it used as well as on the Control Panel; a step that could not be confirmed ended is
reported on the deployment and staff are alerted — read it on the site's deployments (corestack_deployments_get, in
the row's stop_termination) or, for a CoreStack Enterprise environment, on corestack_enterprise_deployment_get
(view.stop_termination). The page shows the same sentence.
Ask for it
Using the Corefinity MCP server, call corestack_deployment_stop with site_id 4211, deployment_id 6610. (Stop a deployment.) Tell me what it returned.Inputs
deployment_idintegerRequired
At least 1.
site_idintegerRequired
At least 1.
Example call
{
"name": "corestack_deployment_stop",
"arguments": {
"site_id": 4211,
"deployment_id": 6610
}
}If it is refused
| Reason | What to do |
|---|---|
managed_elsewhere | 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. |
forbidden | The person's role lacks the Stop Deployments permission. The message names it and says an owner of the company can grant it in Roles; details.permission is stopDeployments. Nothing is changed. |
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. |
The same task elsewhere
Was this helpful?