Recipe: clear POM Cache after a verified change

Use this recipe only when the underlying content or setting is correct but the public page still appears stale. The built-in cache integration can report POM Cache status and clear its cache; it is not a general server, CDN, browser, or object-cache control panel.

Inspect the changed object and confirm the saved value first. Then call the
POM Cache status tool. If POM Cache is active and the user has authorized a
cache clear, call pom_cache_clear. Read the status again and report exactly
what was cleared. Do not repeat the content write and do not claim that an
external CDN or browser cache was purged.

Why verification comes first

Clearing cache cannot repair a failed post update, wrong template assignment, invalid shortcode, or unsaved theme setting. Repeating the original write can instead create duplicates or overwrite newer edits.

Expected result

The client should show:

• the object or setting read back before the clear;
• POM Cache availability;
• the clear result or a reason it could not run;
• the public URL that still needs a browser-level check.

MCP cache operations consume no POM AI credits. They still require the capability enforced by the POM Cache integration.

Related guides: POM Cache tools, limited cache access, and cache workflow.