Publishing a Channel

Every edit to a channel, yours or one you ask Aimée to make, lands on a draft first. Your edits reach the live feed when you click Publish.

Updated November 18, 2026

Edits land on a draft, not the live feed#

When you change a channel's settings, fields or rules, by hand or by asking Aimée in chat, the change is saved to a draft. The live feed stays as it is, so you can experiment without affecting what destinations read.

Used for is different: it applies at once, with no publish step. See Working with channels.

Templates and a project's product sets work the same way. Each has its own draft and its own Publish button, and publishing one doesn't publish the others.

Unpublished changes#

The channel page's header has Revert to published version and Publish buttons, and shows "Unpublished changes" when the draft differs from what's published. With nothing to publish, both buttons are disabled.

  • Revert to published version resets the draft to the published version. Your unpublished work is saved to version history first, so you can restore it.
  • Publish starts a run that writes your draft to the live feed, and marks the version holding it as Published. Renable saves a new version only when none holds your draft yet, so publishing right after Save as version adds no second copy.

What Publish actually does#

The run starts within about 15 seconds and writes to the same URL your destinations already have. It takes longer to finish on a large catalog or while media is rendering.

The live feed changes when the run finishes. If your change needs new images or videos, the feed keeps its previous contents until they're ready, which usually takes a few minutes. The same wait applies while a design's feed image (Image link or Additional image link) is being fetched for the first time. See When a template or prompt first uses a feed image.

A design whose image isn't ready yet isn't missing content, and no rule treats it as missing: the run waits for it. The Preview tab starts the images and voice-overs it shows, so it shows such a design as rendering. Trace only looks and starts nothing. Under each design it says Rendered, Rendering now or Not rendered yet, and voice-overs read as made or not made yet. Trace shows the version you're editing, so a design that isn't rendered yet is made now when you open the Preview tab, and by a channel run once that version is live. If Trace couldn't check a design in time, it says so and checks again.

After an hour, Renable publishes what it has. Products whose images or videos still aren't finished go out archived or out of stock, depending on the channel's rules, for that one run, and come back on the next. A warning on the channel says it happened and how many images were still being made. It takes an unusually large catalog or a slow template to reach the hour. So if your live feed has a product archived or out of stock while Trace shows one of its designs rendering now or not rendered yet, a run went out without that design, and the next run puts it back.

Out of credits, there's no wait: a design that needs a new render goes out with missing content. See What happens when I run out of credits.

A design that is only waiting for a feed image, and whose image placeholder has a fallback, goes out made with the fallback instead. There's no warning, and a later run corrects it once the image arrives.

To skip the wait, use Regenerate. It runs the published channel without waiting for media, so products with unfinished media go out archived or out of stock for that run and return on the next. Publish and automatic runs wait, and so does a queued run you start with Start now. A monitor holding the publish holds Regenerate too. See Working with channels.

Automatic runs only use the published channel#

Renable also runs channels by itself: when your catalog's product feed refreshes each hour, when a price or stock level changes, and when you publish a template or a product set the channel uses. These runs update the live feed from the published channel, so your draft stays out of the feed until you publish.

They are queued first and start within about five minutes, so that several changes share one run. Start now on the Activity tab starts a queued run sooner: see When a run is queued.

Where version history lives#

Every published state is kept as a version. Past versions are in the timeline of the Aimée chat drawer, as template versions are. Open the drawer while viewing the channel to see them and restore one.

Where to go next#