Clear the JSON cache manually

Use the dedicated JSON tool when progressive archive batches are stale or when you need a clean generation test without discarding static HTML.

What the action removes

Delete Progressive JSON Cache removes the complete progressive JSON tree for the current site. It does not remove:

• static HTML files;
• browser cache;
• CDN objects;
• files belonging to another multisite site;
• source posts, terms, translations, or media.

The JSON master switch does not need to be enabled for deletion. This lets you remove old files as part of a shutdown or rollback.

Use the settings tool

On a single site:

1. Open Settings → POM Cache → General;

2. Scroll to Progressive JSON tools;

3. Review Progressive JSON Cache Contents;

4. Select Delete Progressive JSON Cache;

5. Wait for the inline confirmation:

   Progressive JSON cache deleted for the current site.

6. Confirm the summary reports zero cached JSON files.

On multisite, use Network Admin → Settings → POM Cache → General for the site represented by the current context. To clear both HTML and JSON for a particular subsite, the administration-bar method while viewing that site is often the clearest current-site control.

The settings action requires permission to manage POM Cache settings.

When to use it

Manual JSON clearing is appropriate after:

• changing progressive archive templates or batch size;
• changing display settings that alter JSON but have no automatic purge integration;
• completing a bulk import or translation batch;
• changing public routes or locale prefixes;
• testing cold versus warm performance;
• moving the cache location;
• disabling direct server delivery;
• diagnosing invalid or oversized stored JSON.

Normal post, term, and translation editing can use the opt-in automatic switches instead.

Do not confuse the two buttons

The General tab contains two separate tool sections:

The administration-bar Delete Cache shortcut is different: it deletes both HTML and JSON for the current site.

Verify regeneration

After the JSON-only clear:

1. Load the archive HTML and confirm it can still be served from the HTML cache if enabled;
2. Trigger a progressive batch;
3. Look for X-POM-Progressive-Archive-Cache: generated-cacheable;
4. Confirm the JSON count increases;
5. Repeat the exact batch URL;
6. Confirm an early PHP or WordPress fallback hit;
7. Verify changed posts, terms, or translations are visible.

If the count does not return, check JSON writes, response cacheability, maximum size, and directory permissions.

Coordinate with a CDN

Deleting the origin file does not send a purge to CloudFront or another CDN. Use this order:

correct source data
→ delete POM Cache JSON
→ verify regenerated origin JSON
→ invalidate affected CDN viewer paths
→ verify public response

Invalidating the edge first can cause it to refill immediately from an origin file you have not yet corrected.

Read Decide when the CDN must also be invalidated before using a broad wildcard.

If deletion is skipped

POM Cache extensions can deliberately prevent a current-site deletion. In that case the tool reports that deletion was skipped by configuration rather than claiming success.

Confirm the authorized site configuration and retry. Do not delete an unverified broad cache path manually. The supported action contains its work to the current site's JSON namespace.