corestack_ error_ pages_ history_ list
List an environment's error pages history.
When to use it
List an environment's error pages revisions, newest first, 20 a page: who changed what and when (author, created_at), the note, how the revision came about (origin: save, revert, reset, copy or birth) and its status (pending, applying, applied, applied_unverified, rejected or unknown). Every change, revert, reset and copy is a revision. Pass next_cursor back as cursor for the next page.
With revision_id the answer is that one revision: revision (its history row), config (its codes, pages and support email) and pages, each page's source before and after that revision with a diff. Read it to compare, or put it back with corestack_error_pages_revert.
Ask for it
Using the Corefinity MCP server, call corestack_error_pages_history_list with site_id 4211. (List an environment's error pages history.) Tell me what it returned.Inputs
next_cursor from the previous page. Up to 512 characters.
One revision, with its configuration and sources. At least 1.
The environment row. At least 1.
Example call
{
"name": "corestack_error_pages_history_list",
"arguments": {
"site_id": 4211
}
}If it is refused
| Reason | What to do |
|---|---|
tenant_mismatch | The environment has no revision with that id (or the environment is not yours). |
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. |