CorefinityCorefinityDocs
Open the Control PanelControl Panel
Deployments · 54 of 65

corestack_enterprise_deployment_retry

Retry a CoreStack Enterprise deployment.

Scope writeRuns as a taskNo secrets returned
On this page

When to use it

Run a CoreStack Enterprise deployment again, as the same row, built from its pipeline as it is now: the list's and the page's Retry. Usually for a failed or cancelled deployment, or to deploy the live release again.

With from: failed_step it is the page's "Retry from the failed step" instead: a failed deployment carries on from the step that failed, in the same release, and no step that finished runs again. Only where the page offers it: read the deployment with corestack_enterprise_deployment_get first, and send failed_step only when its view.actions lists retry_from_step. Anywhere else the tool refuses retry_from_step_unavailable and nothing starts; retry from the start instead (leave from out).

Retrying a deployment that is not the environment's newest puts its older commit live over the newer one. The tool refuses it with confirm and a message naming both deployments. Show the person that message, and only once they agree, call again with confirm_older: true. Retrying the newest deployment needs no confirmation.

A task follows the deployment to its end. The public API's POST /api/environments/{environment}/deployments/{deployment}/retry answers the same, with the same confirm_older and from.

Ask for it

Prompt
Using the Corefinity MCP server, call corestack_enterprise_deployment_retry with enterprise_env_id 1530, deployment_id 185172. (Retry a CoreStack Enterprise deployment.) Tell me what it returned.

Inputs

confirm_olderboolean

Required, as true, to retry a deployment that is not the environment's newest

deployment_idintegerRequired

At least 1.

enterprise_env_idintegerRequired

A CoreStack Enterprise environment's id; for CoreStack or CoreCluster use the corestack_deployment_* tools. At least 1.

fromstring

Where the retry starts. start runs the whole pipeline again; failed_step carries on from the step that failed, where the deployment's page offers it Defaults to start.

startfailed_step

Example call

tools/call
{
  "name": "corestack_enterprise_deployment_retry",
  "arguments": {
    "enterprise_env_id": 1530,
    "deployment_id": 185172
  }
}

If it is refused

ReasonWhat to do
retry_from_step_unavailable"Retry from the failed step is not available for this deployment, so retry it from the start instead." The page does not offer it for this deployment (it has not failed, the step that failed cannot be run again on its own, something it depends on changed since, or it is not available on this environment). Call again without from.
confirmThis is not the environment's newest deployment, so retrying it puts an older release live. The message names the commit and date of both; ask the person before you send confirm_older: true.
staleThe deployment moved on, or cannot be retried in its current state (a legacy scheduled deployment can only be cancelled). Read it again.
artifact_prunedThis deployment's archive was removed after 30 days, so it can't be retried. Deploy again from the commit (corestack_enterprise_deployment_trigger). Archives are kept for 30 days, and always for an environment's 10 most recent deployments and its newest successful one.
busyThe same retry is still being applied. forbidden: the person's role lacks the Retry Deployments permission (a retry from the failed step asks the same). The message names it and says an owner of the company can grant it in Roles; details.permission is retryDeployments.
invalid_argumentsOn enterprise_env_id, a CoreStack or CoreCluster environment (use corestack_deployment_retry by site_id); on from, anything but start or failed_step.
tenant_mismatchThe object does not exist or the token may not see it. Check the id.
pin_refusedThe grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it.
scope_requiredThe token lacks a scope this call needs. Open the link in the answer to add it, then call again.
rate_limitedToo many calls. Wait for the number of seconds the answer names.
temporarily_unavailableThe Control Panel could not answer just now. Nothing was started; try again shortly.
internal_errorSomething went wrong on our side. Quote the trace id to support.

The same task elsewhere

Was this helpful?
Open in ClaudeOpen in ChatGPT