Hold a Channel's Publish When Something Looks Wrong

A monitor can hold a channel's publish when the numbers look suspicious. The previous feed stays live, and the hold clears on its own when a check passes.

Updated November 6, 2026

A broken import can empty half a catalog, and the next channel run would publish that. A monitor with Hold the publish stops it: the previous feed stays live until the problem clears.

Set it up#

  1. Create a monitor that checks after each catalog import or after each channel run. The hold is only available on these two. See Create a monitor. A good starting point is the Channel loses products — hold the publish suggestion on the Monitoring page.
  2. Set the condition that means something is wrong, for example Product count change % is less than -40. Don't leave it empty: a hold with no condition holds every publish it watches and never clears. Feeds then only go out through Publish on the alert, until you pause the monitor, remove the hold or add a condition.
  3. Under Then, click + Add action and pick Hold the publish. A hold always raises an Error alert, so you don't need Raise an alert as well.
  4. Publish the monitor.

A monitor on a catalog holds every channel that exports that catalog's products, so a bad import is stopped before it reaches any destination. A monitor on a channel holds that channel.

On a catalog monitor, a condition on change can clear by itself. The next import compares with the one that tripped the monitor, sees little change and passes, so the next run publishes the same shrunken data. If the hold must last until someone fixes the feed, use a condition on the level instead, for example Product count is less than 5000, with a number that suits your catalog.

What you'll see while a publish is held#

  • The channel page shows a Publish held chip next to its status.
  • The channel's Activity tab shows the held run with the status Publish held, and its detail names the monitor. The previous feed stays live.
  • The monitor's Error alert appears on the dashboard and on the affected catalog or channel.

How it clears#

Fix the problem, and the next import or channel run that passes the condition clears the alert. There's nothing to release by hand.

A channel run that passes publishes as usual. Any other way of lifting a hold, such as an import that passes or pausing the monitor, publishes nothing by itself: the feed stays as it is until the channel's next run. To update it straight away, press Regenerate on the channel page.

Publishing anyway#

If you've looked at the data and it's fine, say the assortment really did halve because a season ended, you don't have to wait:

  • Press Publish on the monitor's alert and confirm. You'll find it on the dashboard, the project's Overview, the channel's Activity tab or the Monitoring page. An alert about a catalog publishes every channel exporting that catalog, and names them first.
  • Or press Publish on the channel page. Renable tells you which monitor is holding the publish and offers Publish anyway.

Either way, you publish that one run. The alert stays until a check passes, so if the monitor was right after all, the next run is held again. If another monitor is holding one of the same channels, publishing anyway goes past that hold too, and the confirmation names it first.

If a monitor holds publishes too eagerly, loosen its condition, or pause it with the switch on its card, which lifts the hold immediately.

Good to know#

  • You can keep editing and previewing the channel while a publish is held. Regenerate is held too.
  • Switching a channel to a held catalog holds its next publish, and switching away releases it. Publish tells you first, and so do Aimée and connected agents when asked to publish.
  • Archiving the alert doesn't lift the hold, and Renable won't let you archive it while a publish is held. To end the hold, press Publish on the alert, fix the problem or pause the monitor.
  • Pausing or archiving the monitor clears its alerts and lifts the hold right away.
  • Hold the publish doesn't apply to alerts already raised. It starts at the next check that triggers.
  • Removing the action lifts the hold when you publish the change. The alert stays until the monitor's next check, and you can't archive it until then.
  • Taking a catalog or channel out of the monitor's scope also lifts the hold when you publish. The monitor no longer checks it, so its alert goes only when you pause or archive the monitor, and you can't archive the alert itself.
  • If an error stops Renable from evaluating the monitor at all, the publish goes ahead.
  • Run status and Publish failed can't hold a publish, because they're only known after the run. Renable won't publish a holding monitor that uses them. Without a hold, a monitor's alert and emails can use them.
  • A monitor can also send a webhook when a hold starts (Triggered) and ends (Cleared). On a monitor that watches channels, the message gives the held run's status as blocked. See Send monitor events to a webhook.