litespeed/update-scheduled-purge configures the daily scheduled purge: a list of URLs, and the time of day to purge them.
It is for pages that go stale on a schedule nothing in WordPress knows about.
At a glance
| Ability | litespeed/update-scheduled-purge |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Purging |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
Most staleness has an event behind it — a post is published, a product is edited — and the automatic purge rules handle those. Some does not: a page that renders “events this week”, a listing driven by an external feed, a banner that should change at midnight.
None of those change anything in WordPress, so nothing purges them, and their TTL is the only thing keeping them current. A scheduled purge at the right hour is a better answer than shortening the TTL for the whole site.
The time is a single daily slot, so choose the hour by when the content actually changes rather than by traffic. A purge at 3am costs almost nothing; the same purge at 9am rebuilds pages while people are reading them.
The URL list is replaced by what you send.
The write is a patch, not a replacement. Send one key and one key changes; everything else in the area is left alone. The response names the keys that actually moved, so a payload that matched the existing values comes back with an empty list rather than a misleading success.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
settings | object | Yes | A map of setting key to new value. Keys outside this area are refused, and the refusal lists what the area accepts. |
What comes back
| Name | Type | What it is |
|---|---|---|
updated | array | The keys that actually changed. An empty array means every value you sent was already set. |
settings | array | Every setting in the area after the write, in the read shape. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Purge the events page every night at 1am.
It resolves to one call:
{
"ability": "litespeed/update-scheduled-purge",
"parameters": {
"settings": {
"purge-timed_urls": ["https://example.com/events/"],
"purge-timed_urls_time": "01:00"
}
}
}Worth knowing
- Better than shortening the site-wide TTL for a handful of time-sensitive pages.
- Choose the hour by when content changes, then by traffic.
- The URL list is replaced by what you send.
- One daily slot, not a cron expression.
Related abilities
- Get Purge Settings — read the current schedule
- Update Cache TTLs — the blunter alternative
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category