Prebuild, Cache & Deleting

VIDEO WALKTHROUGH

Astro Admin — Prebuild, Cache & Performance: setup guide

2:42

Recorded 14 October 2026 · Narrated walkthrough · English captions

Jump to a chapter 8 chapters

1. 0:00Prebuild, Cache & Performance
2. 0:14Start with current data and layouts
3. 0:33Choose a focused build scope
4. 0:53Review progress and failures
5. 1:14Use the appropriate cache control
6. 1:36Review performance settings separately
7. 2:01Verify the customer result
8. 2:23Your next steps

Read the full video transcript

Astro Admin — Prebuild, Cache & Performance 2026-10-14 — Astro Admin setup

00:00:00 — Prebuild, Cache & Performance
Welcome to the Agentic Ecom Astro Admin guide to prebuild, cache & performance. We're using the Sync Comms storefront to show the current controls. We'll review the workflow with previews, without saving changes to this live store.

00:00:14 — Start with current data and layouts
Open Prebuild Pages after saving your intended presentation changes and running the required syncs. The grid lists homepage, category, product and C M S pages, with built, not-built and failed status filters. Review the current state before choosing a build action.

00:00:33 — Choose a focused build scope
Use the page-type tabs and search to narrow the list. For a small change, select the affected pages instead of automatically rebuilding the whole catalogue. Prebuild current view and Build selected have different scopes. Check the selected count and the visible filter before starting an action on your store.

00:00:53 — Review progress and failures
Built, Not Built and Failed help you inspect the outcome. A started build is not a completed build: wait for it to finish and review failures. Build Remaining is useful when the intended pages have not yet been built. We are only filtering this screen, without starting, stopping or repairing a production build.

00:01:14 — Use the appropriate cache control
Cache Management separates Global, C D N, C M S and Image caches. Use the control that matches the stale content after checking that the correct data and pages were built. A browser hard refresh is another useful check. Purging cache is an operational action, so confirm the scope before using it.

00:01:36 — Review performance settings separately
Performance has network and rendering optimisation settings. Review each option against your deployment and test the effects on real pages. Save Changes applies the selected settings; Recommended and Reset All are broad controls. We are reviewing the screen without changing its configuration. Performance options do not replace a successful build or a functioning checkout.

00:02:01 — Verify the customer result
Open View Storefront after your build finishes. Check a representative homepage, category, product and C M S page, including mobile navigation and current price and stock. If something is stale, work through saved source, sync, prebuild, server or C D N cache, then browser cache in that order.

00:02:23 — Your next steps
To put this into practice, build the intended pages, review completion and failures, check caches and real storefront journeys. Test the complete result on your own staging storefront before publishing. You can follow the written Astro Admin guides at user guides dot Agentic Ecom dot net.

Download videoEnglish captionsDownload transcript

Prebuild is the publish button for the whole storefront. It takes your active presets plus the latest synced data and bakes static pages that load instantly for shoppers. Almost everything you do in the Agentic Admin only becomes visible to customers after a prebuild.

Running a prebuild

1. Make and save/activate your changes (preset, page, style, theme) and run any needed syncs.

2. Open the Prebuild action and start it. It bakes the affected pages; larger stores take longer.

3. When it finishes, the Pages Prebuilt count on the Dashboard updates.

4. Open View Storefront to confirm the result.

What needs a prebuild?

Anything that changes appearance or content: activating a structural preset, publishing a page, applying a style, saving a theme, or syncing new data. When in doubt, prebuild.

Clearing the cache

If you’ve prebuilt but the storefront still serves an old version, the cache is holding the previous page. Clear it so the fresh build is served.

1. Use the Clear Cache action in the Agentic Admin (or your hosting/CDN cache purge if your store sits behind a CDN).

2. Reload the storefront with a hard refresh (Ctrl/Cmd + Shift + R) to bypass your browser’s cache too.

Three caches can hide a change

1. The prebuilt page (fixed by a Prebuild), 2. the server/CDN cache (fixed by Clear Cache / CDN purge), and 3. your browser cache (fixed by a hard refresh). If a change is stubborn, work through all three in that order.

Deleting prebuilt pages / starting clean

To remove baked pages — for example to force a completely fresh rebuild — use the delete / clear prebuilt action, then run a new Prebuild. This is useful when:

• You removed products or pages in Magento and want the stale baked pages gone.
• A build looks wrong and you want to bake it again from scratch.

Caution

Deleting prebuilt pages takes them off the live store until you Prebuild again. On a production store, delete-then-prebuild in a quiet period, or prebuild first and only delete what’s genuinely stale.

When a change isn’t showing

This is the most common question. Work down it in order; one of these is nearly always the cause:

1. Did you save / publish / activate the change in the admin? (A draft isn’t live.)

2. Did you run the right sync? Catalogue change → Sync Products; CMS change → Sync CMS.

3. Did you Prebuild after the change? This is the usual culprit.

4. Did you Clear Cache (and CDN purge if you use one)?

5. Hard-refresh your browser to rule out browser cache.

6. Still wrong? Check the source in Magento is correct, saved, enabled and visible.

Next: Going-live checklist One ordered checklist from empty store to live.