Repair Magento's cache settings
Sets Magento's own cache settings to match the site's Varnish again, for when magento_config.state reads needs_repair. It runs a command on the site: follow it while its status is queued or running. A site takes six repairs an hour, whoever asks and from wherever. The endpoint is not found while site functions are off for the platform.
Path parameters
The id of a site row. A website's production site and each of its environments has its own id. Digits only. At least 1.
Returns
200 The repair finished within the request. command.status is succeeded or failed.
202 The repair is still running. Follow command.
Fields of the 200 answer
A command on the site: a purge, or a repair of Magento's cache settings.
Fields
Why it failed, in plain words.
Format: date-time.
At least 1.
What was asked for. For a purge: its mode, the items it names and where the request came from (via). Null for a repair.
Fields
The one host the purge was limited to, when it was.
alltagsurlspatternsAlways varnish for a purge.
Where the purge was asked for, such as api.
varnish_purgemagento_varnish_configFormat: date-time.
What the command did. For a purge: the requests sent, how many were needed (requests) and whether Varnish confirmed them. For a repair: the cache Magento was set up for (mode: varnish or builtin) and whether anything had to be changed. Null until it finishes.
Fields
For a repair: whether Magento's settings had to be changed.
How many items the purge named; 1 for everything.
For a purge, its mode. For a repair, varnish or builtin: the cache Magento's settings now name.
Present only when the purge has something to warn about: a pattern broad enough to empty most of the cache, or an address too long to purge with its query variants, of which only the exact address was purged.
A site by its id and domain.
Fields
Format: date-time.
queued or running while it runs, then succeeded or failed.
Fields of the 202 answer
A command on the site: a purge, or a repair of Magento's cache settings.
Fields
Why it failed, in plain words.
Format: date-time.
At least 1.
What was asked for. For a purge: its mode, the items it names and where the request came from (via). Null for a repair.
Fields
The one host the purge was limited to, when it was.
alltagsurlspatternsAlways varnish for a purge.
Where the purge was asked for, such as api.
varnish_purgemagento_varnish_configFormat: date-time.
What the command did. For a purge: the requests sent, how many were needed (requests) and whether Varnish confirmed them. For a repair: the cache Magento was set up for (mode: varnish or builtin) and whether anything had to be changed. Null until it finishes.
Fields
For a repair: whether Magento's settings had to be changed.
How many items the purge named; 1 for everything.
For a purge, its mode. For a repair, varnish or builtin: the cache Magento's settings now name.
Present only when the purge has something to warn about: a pattern broad enough to empty most of the cache, or an address too long to purge with its query variants, of which only the exact address was purged.
A site by its id and domain.
Fields
Format: date-time.
queued or running while it runs, then succeeded or failed.
If it is refused
| Status | Reason | What to do |
|---|---|---|
401 | none | Send a valid token as Authorization: Bearer <token>. |
403 | company_unavailable | Your company is unavailable. |
403 | scope_required | Use a token with the scope named in scope. |
403 | two_factor_required | Turn on two-factor on your account, then send again. |
404 | feature_off | This feature is not on for your organisation yet. |
409 | busy | Another operation is running on the site. Wait for it to finish. |
409 | command_running | Another action or command is still running on the site. Wait for it to finish, then try again. |
409 | exec_unresolved | An earlier command on the site has not been confirmed stopped. Contact support. |
409 | managed_elsewhere | This site is read-only here. Change it in the control panel that manages it. |
409 | not_running | The site, environment or deployment is not running. Read the message: where it can be started or will recover, start it or wait, then try again. |
409 | wrong_platform | This is not available for the site's platform. Use it on a site of the platform it is for. |
429 | rate_limited | Wait for the seconds in Retry-After. |
503 | switched_off | Corefinity has switched this action off for the moment. Try again later. |
Reasons are listed by name in Errors and refusals.
The same task elsewhere
curl -X POST https://manage.corefinity.com/api/corestack/sites/1042/varnish/repair \
-H "Authorization: Bearer $COREFINITY_TOKEN" \
-H "Accept: application/json"use Illuminate\Support\Facades\Http;
$response = Http::withToken(env('COREFINITY_TOKEN'))
->acceptJson()
->post('https://manage.corefinity.com/api/corestack/sites/1042/varnish/repair');
$data = $response->json();const res = await fetch('https://manage.corefinity.com/api/corestack/sites/1042/varnish/repair', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.COREFINITY_TOKEN}`,
Accept: 'application/json',
},
});
// An answer with no body (204) has nothing to parse.
const text = await res.text();
const data = text && JSON.parse(text);import os
import requests
res = requests.post(
"https://manage.corefinity.com/api/corestack/sites/1042/varnish/repair",
headers={
"Authorization": f"Bearer {os.environ['COREFINITY_TOKEN']}",
"Accept": "application/json",
},
)
data = res.json() if res.content else None{
"command": {
"blocked_until_verified": false,
"duration_ms": 840,
"error": null,
"exit_code": 0,
"finished_at": "2026-11-06T09:16:41Z",
"id": 906,
"input": null,
"kind": "magento_varnish_config",
"label": "Repair Magento cache settings",
"operation_id": null,
"output_excerpt": null,
"queued_at": "2026-11-06T09:16:40Z",
"requested_by": {
"id": 2041,
"name": "Eleanor Finch"
},
"result": {
"changed": true,
"mode": "varnish"
},
"site": {
"domain": "harbourandfinch.example.com",
"id": 1042
},
"started_at": "2026-11-06T09:16:40Z",
"status": "succeeded",
"status_label": "Done"
}
}{
"command": {
"blocked_until_verified": false,
"duration_ms": null,
"error": null,
"exit_code": null,
"finished_at": null,
"id": 906,
"input": null,
"kind": "magento_varnish_config",
"label": "Repair Magento cache settings",
"operation_id": null,
"output_excerpt": null,
"queued_at": "2026-11-06T09:16:40Z",
"requested_by": {
"id": 2041,
"name": "Eleanor Finch"
},
"result": null,
"site": {
"domain": "harbourandfinch.example.com",
"id": 1042
},
"started_at": "2026-11-06T09:16:40Z",
"status": "running",
"status_label": "Running"
}
}{
"message": "Unauthenticated."
}{
"code": "company_unavailable",
"message": "Your company is unavailable.",
"reason": "company_unavailable"
}{
"code": "feature_off",
"message": "Not found.",
"reason": "feature_off"
}{
"code": "busy",
"message": "Another change to this site is in progress. Wait for it to finish.",
"reason": "busy"
}{
"code": "rate_limited",
"message": "Too many requests. Try again in 60 seconds.",
"reason": "rate_limited",
"retry_after_seconds": 60
}{
"code": "switched_off",
"message": "Site commands are switched off at the moment",
"reason": "switched_off"
}Try it is off for this endpointIt runs commands on a live site. Copy the request and run it yourself when you are sure.