corestack_ varnish_ vcl_ revert
Revert a site's Varnish VCL.
When to use it
Put an earlier custom Varnish VCL revision back on a Magento 2 row. A revert is a new revision (origin revert) with that revision's hooks: it is checked and compiled first, then applied live exactly like corestack_varnish_vcl_update, with the same task (its result's vcl says whether Varnish loaded it), the same automatic put-back if Varnish refuses it, and the same answer while Varnish is off. The history keeps every revision.
Ask for it
Using the Corefinity MCP server, call corestack_varnish_vcl_revert with site_id 4211, number 3. (Revert a site's Varnish VCL.) Tell me what it returned.Inputs
numberintegerRequired
The revision to put back, from corestack_varnish_vcl_history_list. 0 puts back the platform's original, the empty hooks: the platform VCL alone.
site_idintegerRequired
The row, a Magento 2 site or one of its environments. At least 1.
Example call
{
"name": "corestack_varnish_vcl_revert",
"arguments": {
"site_id": 4211,
"number": 3
}
}If it is refused
| Reason | What to do |
|---|---|
tenant_mismatch | The row has no revision with that number (or the row is not yours). |
vcl_invalid | Or vcl_compile_failed: that revision no longer passes the policy or compiles on the row's Varnish version; details.diagnostics. Nothing was saved. |
vcl_locked | Corefinity manages the VCL on this environment. |
busy | A save is already applying; try again when it ends. |
varnish_not_offered | The row is not a Magento 2 site. |
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. |
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. |
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?