---
title: "corestack_pending_changes_apply_now"
url: https://docs.corefinity.com/mcp/tools/corestack_pending_changes_apply_now
type: tool
last_updated: 2026-11-13
feature: pending-changes
related:
  - https://docs.corefinity.com/api/reference/sites/apply-site-pending-changes-now.md
  - https://docs.corefinity.com/guides/sites/size-and-capacity/pending-changes-and-apply-windows.md
---
# corestack_pending_changes_apply_now

**Apply pending changes now.** Apply a row's changes queued for tonight now instead of in the maintenance window. They apply together, in about a minute. Set confirm to true once the person agrees to apply them now. Scope: write. Long-running: answers with a task.

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

## When to use it

Apply a row's changes queued for tonight now instead of in the maintenance window. They apply together, in about a minute. Set confirm to true once the person agrees to apply them now.

## Inputs

- `site_id` (integer, ≥ 1, required)
- `confirm` (boolean, required): true: the person agrees to apply the changes now.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "confirm": {
      "description": "true: the person agrees to apply the changes now.",
      "type": "boolean"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id",
    "confirm"
  ],
  "type": "object"
}
```

## Refusals

- `nothing_pending`: nothing is pending to apply.
- `busy`: another change is running on this row; wait for it (corestack_site_operation_get) and call again.
- `batch_window`: tonight's maintenance window is running and its planner owns the batch; wait until the window has ended.
- `node_full`: no server of the site's compute cluster has room for the site now — none has room for its CPU and memory requests beside the changes already applying, or for its memory limit. A server that is full does not refuse the change while another one can take it. Try again later, or leave the changes for tonight.
- `node_busy`: every server that could take the site is already applying changes to as many sites as it may at once. Try again shortly, or leave the changes for tonight.
- `no_node`: no server of the site's compute cluster is taking sites right now. Try again later, or leave the changes for tonight.
- Any other refusal carries the Control Panel's own sentence in `message`.
- `managed_elsewhere` (message: "This site is managed by another control panel"): 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.
- 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_pending_changes_apply_now",
  "arguments": {
    "site_id": 4211,
    "confirm": true
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_pending_changes_apply_now with site_id 4211. (Apply pending changes now.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [POST /api/corestack/sites/{site}/pending-changes/apply-now](https://docs.corefinity.com/api/reference/sites/apply-site-pending-changes-now.md)
- Guide: [Pending changes and apply windows](https://docs.corefinity.com/guides/sites/size-and-capacity/pending-changes-and-apply-windows.md)
