troubleshooting

Resolving Stale Content & Verifying Edge Update Triggers

Diagnose and fix stale content issues by verifying the WordPress plugin connection and triggering an instant edge rebuild.

📋This is an interactive step-by-step HowTo guide with 3 verified installation steps.

Why Updated Content Might Appear Stale

When you update a post in WordPress Admin, changes should reflect on the edge within seconds. If visitors see older versions of the page, work through the following diagnostic steps:

Common Causes

Local Browser Cache: Your browser may hold an aggressive local disk cache. Test in a Private/Incognito window with DevTools network cache disabled.
Plugin Disconnected: Verify that the Nimbica plugin in WP-Admin shows "Connected ✓" status. If disconnected, reconnect using your API key or email login.
Page Excluded from Auto-Deploy: Custom post types may require explicit inclusion in the auto-deploy settings in your Nimbica dashboard.

📋 Verified Execution Steps (3 Total Steps)

11. Check Plugin Connection Status

In WordPress Admin ➔ Nimbica ➔ Settings, ensure the status indicator displays "Connected ✓".

22. Trigger a Manual Edge Rebuild

Click "Build & Deploy" in the WordPress Admin top toolbar or from your Nimbica Dashboard to force a content refresh.

33. Inspect Response Headers

Open browser DevTools ➔ Network tab, load the page, and check the "x-nimbica-build-id" header to confirm the latest AI build is serving.

Was this documentation page helpful?

Last updated on 2026-09-07