Live or build-time: how Throttle Builder pages reach your store
The two delivery modes of Throttle Builder, in plain words: when a change shows, what each costs on your host, how releases work and how to roll back.
When you publish a page in Throttle Builder, your store has to learn about it. Builder offers two ways, and you choose in Site, then Delivery. You can switch at any time.
The two modes at a glance
| Live | Build-time | |
|---|---|---|
| When a change shows | Shortly after you publish | After you press Release now and your host has rebuilt the store |
| What you press | Publish | Publish, then Release now |
| Good for | Most stores, and anyone who edits often | Stores that want every change reviewed and shipped as one batch, or that want the lowest hosting bill |
| Cost on your host | A page edit refreshes that page. Publishing the theme, menus, brand, header or footer refreshes every page visited next | One full build per release, and nothing else |
| Undoing a change | Edit the page and publish again | Roll back to this on any earlier release |
Live
Live is the default. Your store asks Builder for a page when a shopper first visits it, and keeps it. When you publish, Builder sends your store a signed note saying what changed, and the store refreshes only those pages.
What it costs your host, in plain terms:
- Pages are kept for at least an hour. There is no setting to make that shorter, so nothing refreshes on a timer.
- Publishing a page refreshes only that page. Editing the About page does not refresh the rest of the store.
- Publishing the site settings (theme, menus, brand, announcement) or the header or footer is different. Every page shows those, so every page is rebuilt the next time someone visits it. Make those changes in one go, not one at a time.
- Pages are not built ahead of time. The first visitor to a page waits slightly longer, and everyone after gets the kept copy.
Live needs nothing from you beyond setting it up once.
Build-time
In Build-time, publishing does not change your store. It adds to a list of changes waiting for the next release. Under Delivery, Next release shows that list, for example “changed about” or “added summer-sale”.
When you press Release now, Builder freezes everything published at that moment into one release: your site settings, every page, the header and footer, and the images they use. It then tells your host, through your deploy hook, to build your store from it. That is usually one build per release; if your host does not answer in time, Builder tries again, up to three times in all. Your store makes no request to Builder after that, so it keeps working even if Builder is down.
What it costs your host:
- One full build per release. Every page is built, on purpose.
- Nothing else. Builder causes no page refreshes between releases.
Releases are limited so a slip cannot flood your host: one every 10 seconds and 20 an hour.
The first time
Follow step 6 of the setup guide: make a deploy hook in your host, save it under Delivery, then press Release now. The release says Sent to your store host when your host took the request. If it says your host did not accept it, check the hook address.
Switching modes
- Live to Build-time. Builder asks you to confirm: publishing will no longer update the store by itself. Changes wait for a release. Your developer also has to set the store up for build-time (the developer guide for it is in the Builder docs).
- Build-time to Live. Releases stop, and the store reads published pages as they change.
Changes you published while on Build-time stay published. They go out with the next release, or are read live after you switch back.
Rolling back
On Build-time, open Delivery, find the earlier release under History and choose Roll back to this. Builder asks you to confirm: your store is rebuilt from that release, and pages published since stop being live until you release again. A rollback is itself a new entry in the history, so you can roll forward again the same way. Builder keeps your newest 50 releases.
On Live there is no release to go back to. Open the page, restore an earlier version from its history if you need to, and publish again.
The announcement bar
The announcement can have a start and end time. In Build-time, the pages Builder builds are made once, so a start or end time that passes after a release takes effect with your next release. On shop, search and product pages the bar still turns on and off at its times, with no rebuild.
Which should I pick?
- Choose Live if you are unsure, edit often, or want changes quickly.
- Choose Build-time if you want to review a batch of changes before any of them reaches shoppers, or your host bills for page refreshes and you want the most predictable bill.
Your page addresses, search settings and the look of your store are the same in both modes.