corestack_ error_ pages_ revert
Put back earlier error pages or the defaults.
When to use it
Put earlier error pages back on an environment, or go back to the platform defaults, with the version that corestack_error_pages_get answered.
revision_id: an earlier revision fromcorestack_error_pages_history_list; its codes, pages and support email come back.to: "defaults": the platform's pages and the default settings (500, 502, 503 and 504 show the error page, 404 shows the app's own response).
Send exactly one of the two. Either is a new revision, so it shows in the history, and it is applied exactly like corestack_error_pages_update: the same task, the same error_pages outcome in its result and the same refusals. Pages that are already what you ask for answer {operation: null, revision: null}.
Ask for it
Using the Corefinity MCP server, call corestack_error_pages_revert with site_id 4211, version 5, to defaults, note Back to the platform pages. (Put back earlier error pages or the defaults.) Tell me what it returned.Inputs
notestring
Why, shown in the history. Up to 200 characters.
revision_idinteger
The revision to put back. Not with to. At least 1.
site_idintegerRequired
The environment row. At least 1.
tostring
The platform defaults. Not with revision_id.
defaultsversionintegerRequired
The version from corestack_error_pages_get. At least 0.
Example call
{
"name": "corestack_error_pages_revert",
"arguments": {
"site_id": 4211,
"version": 5,
"to": "defaults",
"note": "Back to the platform pages"
}
}If it is refused
| Reason | What to do |
|---|---|
tenant_mismatch | The environment has no revision with that id (or the environment is not yours). |
stale | Someone changed the pages since version was read. |
error_pages_locked | Corefinity has locked this environment's error pages. |
invalid_page | overlap_nginx_rules, too_large, runtime_lacks_capability, operation_in_progress, switch_reconcile_failed, managed_elsewhere: as corestack_error_pages_update. |
feature_off | Error pages are not available to you yet. |
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?