corestack_ site_ restore_ deleted
Restore a deleted site.
When to use it
Bring back a site deleted with corestack_site_delete while it is still in its grace period.
Ask for it
Using the Corefinity MCP server, call corestack_site_restore_deleted with site_id 4211. (Restore a deleted site.) Tell me what it returned.Inputs
site_idintegerRequired
The deleted site's id (its production row). At least 1.
Example call
{
"name": "corestack_site_restore_deleted",
"arguments": {
"site_id": 4211
}
}If it is refused
| Reason | What to do |
|---|---|
not_restorable | Only a production row in its grace period can be restored. A site deleted while its create was still waiting for a tested version was never set up, so there is nothing to restore (message: "This site was deleted before it was set up, so there is nothing to restore. You can create it again."). |
provisioning | The site is still being created; wait for corestack_site_provisioning_get to finish. |
capacity_blocked | The site's CoreCluster has no room for it now (a deleted site stops counting against the cluster's disk once its deletion has finished, so the room may have been used since). Restoring it is checked as creating it would be: with automatic upgrades on (corestack_company_auto_upgrades_get), the CoreCluster first grows within the company's monthly limit; otherwise, or over the limit, the message says what is short. Free some room or upgrade the package (corecluster_upgrade_options_get), then try again. Nothing was restored. |
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. |
rate_limited | The person has restored as many deleted sites this minute as the limit allows (10 by default, shared with the Control Panel and the API; deleting sites never uses it up). A restore that is refused does not count. Wait retry_after_seconds, then call again. |
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. |
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?