Skip to content

Keeping your content up to date

Your catalogue changes. Prices move, products arrive, descriptions get rewritten. Keeping Rubikc current means running the same two stages again. Syncs can run on a schedule; transforms you run yourself.

That is the Preserve edited blocks step, and it is on by default. Generated blocks you have not edited are updated, which is how a changed description reaches your storefront. Blocks you created yourself are left as you wrote them. See Running a transform again.

To replace an edit with what the Source says now, turn Preserve edited blocks off for that run. The edit stays in the block’s Block history, where you can restore it as a draft. Transform logs lists each block it left alone under Kept as-is.

Sync whenever you want current data. It is always safe.

Transform when you want that data reflected in your cubes. Transforming is also how you apply different choices to content you have already built.

An automation runs a sync on a schedule — every hour, every 6 hours, every day or every week — so your Sources stay current without you remembering. A Bókun Space can also turn on Available days there, which updates the Available filter. See Automations.

A daily sync suits a catalogue that changes often; weekly is plenty for most.

Nothing interrupts you when a scheduled sync goes wrong, so it is worth checking occasionally.

  • Sync logs for problems pulling data in, including scheduled syncs.
  • Transform logs for problems building cubes from it, including a transform that ran after a sync.