---
title: "corestack_error_pages_revert"
url: https://docs.corefinity.com/mcp/tools/corestack_error_pages_revert
type: tool
last_updated: 2026-11-13
feature: error-pages
related:
  - https://docs.corefinity.com/api/reference/site-settings/restore-site-error-page-revision.md
  - https://docs.corefinity.com/guides/sites/site-settings/error-and-maintenance-pages.md
---
# corestack_error_pages_revert

**Put back earlier error pages or the defaults.** Puts an earlier error pages revision back (revision_id) or the platform defaults (to: defaults), with the version from corestack_error_pages_get. Scope: write. Long-running: answers with a task.

- Scope: `write`
- Runs as a task: yes

## 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 from `corestack_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}`.

## Inputs

- `site_id` (integer, ≥ 1, required): the environment row.
- `version` (integer, ≥ 0, required): the version from `corestack_error_pages_get`.
- `revision_id` (integer, ≥ 1): the revision to put back. Not with `to`.
- `to` (string): `defaults`. Not with `revision_id`.
- `note` (string, at most 200 characters): why, shown in the history.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "note": {
      "description": "Shown in the history.",
      "maxLength": 200,
      "type": "string"
    },
    "revision_id": {
      "description": "From corestack_error_pages_history_list. Not with to.",
      "minimum": 1,
      "type": "integer"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    },
    "to": {
      "description": "The platform defaults. Not with revision_id.",
      "enum": [
        "defaults"
      ],
      "type": "string"
    },
    "version": {
      "minimum": 0,
      "type": "integer"
    }
  },
  "required": [
    "site_id",
    "version"
  ],
  "type": "object"
}
```

## Refusals

- `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.
- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_error_pages_revert",
  "arguments": {
    "site_id": 4211,
    "version": 5,
    "to": "defaults",
    "note": "Back to the platform pages"
  }
}
```

## Prompt

```text
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.
```

## The same task elsewhere

- Endpoint: [POST /api/corestack/sites/{site}/error-pages/revert](https://docs.corefinity.com/api/reference/site-settings/restore-site-error-page-revision.md)
- Guide: [Error pages](https://docs.corefinity.com/guides/sites/site-settings/error-and-maintenance-pages.md)
