Monitoring Your Catalogs and Channels

Monitors watch your catalogs and channels and alert you when something needs attention, such as a shrinking product count, a failed import or a field going empty. They can also send email and webhooks, and hold a channel's publish so the previous feed stays live until the problem clears.

Updated November 6, 2026

A monitor is a rule that keeps an eye on your catalogs and channels so you don't have to. You describe what to watch for, such as "product count drops sharply", "no successful import in a day" or "the price field starts going empty", and Renable raises an alert when it happens. You'll find your monitors on the Monitoring page in the top navigation.

Build one yourself on the monitor page, or ask Aimée: "warn me if the price field starts going empty".

What a monitor can watch#

Each monitor checks one kind of thing:

  • After each catalog import: product count and how much it changed, new and removed products, how many warning types the import raised, how full each field is, or whether it failed. Its Run status is OK, Issues, Warnings or Errors. An import that found the feed unchanged isn't checked.
  • After each channel run: how many products made it in, how many were excluded, out of stock or archived, how much those numbers changed since the last run, or whether the run failed. Its Run status is Published, Published with warnings, Publish held or Failed. The monitor checks after every run that finishes, including one that was held or failed, but not one that only emptied the feed.
  • When an event is reported: warnings and errors as they appear anywhere in your account, filtered by how serious they are. This is useful for relaying anything that needs attention to your inbox.
  • On a schedule: conditions about time, such as a catalog with no successful import for too many hours, or a channel that hasn't published in a while. Latest run status shows how the most recent import or channel run ended, and a catalog's can also be No changes, Retrying or Skipped. Retrying isn't a failure: the import was cut short and is being tried again, and monitors that check after each import wait for the result.

A monitor can watch all your catalogs or channels, or just the ones you pick. One watching all catalogs checks each separately, so if two catalogs shrink, you get an alert on each.

What happens when a monitor triggers#

When the condition holds, the monitor triggers and does what its actions say: Raise an alert, Send an email, Hold the publish, Send a webhook, or any mix of them.

  • An alert appears on your dashboard's attention list and on the affected catalog or channel's Activity tab, and stays there for as long as the problem persists.
  • An email goes out once when the monitor triggers, with no repeats at later checks.
  • A webhook sends a message to another system when the monitor triggers, when it clears, or on every check where the condition holds. You choose which.
  • When a later check passes, the monitor clears on its own and its alert disappears. A failed import or channel run never clears it.

A monitor's card and status line show where it's triggered right now. Its Activity tab keeps the newest 50 events: each time it triggered or cleared, and the emails and webhooks that went with them.

You choose whether an alert is a Warning or an Error, except that a monitor holding the publish always raises an Error. Write your own alert text, or leave it empty for an automatic summary of what was observed. You can insert observed values, the affected catalog or channel, and links back into the app from a list. The email can have its own title and text, written the same way.

A monitor with no condition#

The condition is optional, and a monitor without one matches every check.

  • After imports or channel runs: it triggers on the first check and stays triggered, so it emails once. The project's status reads Needs attention, and publishing shows this note: "This monitor has no condition, so its alert is raised on every catalog it watches and never clears — each of those catalogs shows as needing attention until you pause the monitor or add a condition."
  • On events: it clears again once none of the events it watches is open.
  • On a schedule: a condition is required, and publishing is refused without one.

Holding a channel's publish#

A monitor that checks catalog imports or channel runs can also hold the publish. When it triggers, the previous feed stays live on affected channels instead of the suspicious new one. The hold clears on its own as soon as a check passes.

While a publish is held, the channel page shows a Publish held chip, and the channel's Activity tab shows the held run. If you're confident the data is fine, press Publish on the monitor's alert, or on the channel page, which asks you to confirm with Publish anyway. Publishing anyway doesn't clear the alert, and you can't archive the alert while the publish is held. See Hold a channel's publish when something looks wrong.

Email alerts#

Send to members of your team, or to any other address, such as a client or a shared inbox. Addresses outside your team must click a verification link before any alerts are sent to them.

A monitor can send more than one email, each to its own people and with its own wording: a short plain-language note to the store owner, say, and a technical one to a shared team inbox. See Email alerts and verified addresses.

Webhooks#

Send a webhook connects a monitor to another system, such as a CRM, a ticketing tool or an automation platform. Renable sends a JSON message to the https address you enter, and that system acts on it, for example by turning every triggered monitor into a task for someone on the team.

Each webhook chooses its events, Matched, Triggered and Cleared, and Send test checks the address before you publish. A delivery that keeps failing raises an Error alert on the monitor. See Send monitor events to a webhook.

The monitors you start with#

A new organization starts with three monitors, already on:

  • Import fails: raises an Error alert when a catalog import fails.
  • Publish fails: raises an Error alert when a channel run fails.
  • Product count drops sharply: raises a Warning alert when a catalog shrinks more than 30% between imports.

Each one also emails whoever was a member of your organization when it was created, which at signup is you. People who join later aren't added automatically. You can change who gets the email, adjust the threshold, pause or archive them like any other monitor.

Pausing, editing, and archiving#

  • The switch on each monitor card, and on the status line at the top of the monitor page, turns it on or off immediately, without publishing. Pausing a monitor clears its open alerts.
  • Edits are drafts: nothing changes until you press Publish on the monitor page. Every published version is kept in history. A monitor checks nothing until you first publish it.
  • Monitors are archived, never deleted, from the card's menu or the status line's menu. Archiving clears the monitor's open alerts and keeps its history.
  • When you archive a catalog, a channel or a whole project, monitors stop checking it and clear what they had triggered on it.

Where to go next#