Staleness and re-publishing
Editing a shared block never changes a published version. The trade-off is that published templates can fall behind their blocks. Maiilo tracks this for you.
When a template is stale
Section titled “When a template is stale”A template is stale when a shared block it uses was edited after the template’s published version was created.
- A stale template still works. The API and SendGrid keep serving its published version, with the old block content.
- A template that has never been published is never stale, because nothing has been frozen yet.
- Staleness is worked out fresh each time you load a page, so it is always current. There is nothing to dismiss or mark as read.
Clear it by re-publishing
Section titled “Clear it by re-publishing”Re-publishing a stale template creates a new version that includes the current block content, and the template stops being stale straight away.
Re-publishing publishes the template’s whole current draft, not only the block change. If the draft has other unpublished edits, they go live too.
Where to re-publish
Section titled “Where to re-publish”- One template: press Publish in the builder, or Re-publish on its row in Needs Attention.
- Many templates: on Needs Attention, stale templates are grouped by the block that changed. Every row starts ticked. Untick any you want to hold back and press Re-publish all N (or Re-publish N selected).
A batch re-publish asks you to confirm, then publishes the templates one at a time. If one fails, the others are still published. The one that failed stays stale, so running the batch again retries exactly the templates that did not make it.
After re-publishing
Section titled “After re-publishing”Re-publishing creates a new version, so any template you push to SendGrid now shows SendGrid as behind. Push it again to update SendGrid.