litespeed/test-object-cache-connection opens a connection to the configured object-cache backend and reports whether it succeeded.
Read-only, and the right call immediately after changing any backend setting.
At a glance
| Ability | litespeed/test-object-cache-connection |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Object & Browser Cache |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
When LiteSpeed cannot reach the object-cache backend it does not warn, log prominently or disable the feature. It falls back to the database and carries on.
From the outside that is indistinguishable from working, except that the site is slower than it should be — which is exactly the symptom people attribute to everything except the cache that is meant to be fixing it.
A wrong port, a firewall rule, a backend that was restarted onto a different host, credentials that expired: all of them produce the same silence. This call breaks it.
Run it after every change to the host, port, credentials or backend type. Run it also when a site has become mysteriously slower and nothing in the code changed — an object cache that quietly stopped answering is a common cause.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
connected | boolean | Whether the connection succeeded. |
backend | string | Which backend was tried. |
error | string | The failure reason, when it failed. |
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:
Can we actually reach the Redis server?
It resolves to one call:
{
"ability": "litespeed/test-object-cache-connection",
"parameters": {}
}Worth knowing
- LiteSpeed falls back to the database silently. This is the only positive confirmation.
- Run it after every backend settings change.
- A site that got slower for no reason is worth testing here.
Related abilities
- Update Object Cache Settings — fix the configuration
- Get Object Cache Status — the drop-in side of the question
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category