corestack_ site_ live_ refresh
Refresh a site's live status.
When to use it
Read a site's pod health and live status from its cluster now (at most every 15 seconds), then answer the site as corestack_site_get does.
Ask for it
Using the Corefinity MCP server, call corestack_site_live_refresh with site_id 4211. (Refresh a site's live status.) Tell me what it returned.Inputs
site_idintegerRequired
At least 1.
Example call
{
"name": "corestack_site_live_refresh",
"arguments": {
"site_id": 4211
}
}If it is refused
| Reason | What to do |
|---|---|
pin_refused | The environment shown for this site is outside the token's pins. This is checked before reading live status or changing settings, including for existing tokens when a site becomes staging-only. Add the site using the returned link, or address a covered environment by its own site_id. The refusal names only the requested row. A successful reply describes the environment admitted at the start of that call, even if the display environment changes while work runs; the next call checks the current display environment again. |
upstream_unavailable | The Control Panel answered 502: the cluster, a DNS resolver, Cloudflare, Mailgun, a Git provider, Google, Xero or Cloud Storage did not answer; details.upstream names it; retry later. |
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. |
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?