A shared pattern edit is a multi-page change. List its consumers and verify both the saved content and public responses.
Confirm the content relationship
Identify whether the component is a synced pattern, a detached copy or ordinary blocks copied earlier. Record the pattern and pages that use it. Detached content is not expected to inherit later edits. Before cache diagnosis, inspect a saved consumer in the editor and verify that it references the intended shared pattern.
Build a representative consumer list
Include a post, landing page and shared template if relevant. Add paginated or archive surfaces only when they actually render the pattern. On staging, change a harmless text marker. Record the old and new values and publish the pattern through the supported editor workflow. Avoid testing with a live legal or payment instruction.
Compare saved content with delivery
Check each consumer’s public document response in a guest session. If the editor’s saved reference is correct but HTML is old, investigate the corresponding cached page. If one consumer is detached, no purge will reconnect it. Keep content relationship and delivery-layer findings separate so the fix reaches the responsible owner.
Check invalidation coverage
Purge one stale consumer at the identified layer to test the diagnosis, then ask how future pattern edits invalidate dependent pages. A permalink-only purge can miss shared-template consumers. Use supported dependency-aware tooling where available and document the fallback scope. Do not assume every cache integration tracks pattern relationships.
Verify change and restoration
Repeat the pattern edit after the proposed correction, then restore the test text. Check all listed consumers without manual intervention where expected. Include a normal repeat visit and a clean guest visit. Preserve the pattern revision and dependency list as a regression test when the editor or cache integration updates.
Symptom-to-cause worksheet
| What you observe | What to investigate | Next check |
|---|---|---|
| One consumer never updates | Detached or different pattern | Inspect saved reference |
| Editor correct, guest HTML old | Dependent page cache stale | Compare document and targeted purge |
| Manual purge fixes only temporarily | Dependency invalidation gap | Repeat pattern publication |
Worked investigation scenario
Illustrative investigation, not a measured Velonic result. Imagine a shared callout updates on an uncached landing page but remains old on two warm articles. Verify their pattern references, then purge one article to locate the stale layer. A durable fix must handle both dependent articles on the next pattern edit. Keep a detached copy outside that acceptance set unless the content owner explicitly chooses to reconnect it.
Put it into practice
- Distinguish synced references from detached copies.
- List consumers before changing shared content.
- Verify the next edit and restoration.
AI-assisted educational content prepared for the Velonic resource library. How these guides are prepared.