🇺🇦
3 min read

Daily digests for routine visual check results

RenderLog can send urgent run alerts immediately and group routine visual check summaries into a daily digest.

notificationsvisual monitoring
On this page
  1. Not every visual check needs an immediate alert
  2. How teams use digests
  3. Alert or digest?
  4. Set the first notification rhythm

Use this when

  • Use every run for urgent checks and broken-page signals.
  • Use a daily digest for routine history and stable scheduled checks.
  • Digest time is stored in UTC and shown with local time in the app.
Daily digests for routine visual check results

Not every visual check needs an immediate alert

Visual monitoring gets noisy when every successful run sends a message. Some checks need immediate attention: a failed release check, a missing selector, a login wall or a page that no longer matches its baseline. Routine history can wait.

RenderLog separates notification destinations from cadence. A workspace, Product or Check Suite can keep the same destination while individual run settings decide whether messages are off, sent for every run or grouped into a daily digest.

How teams use digests

A marketing team can receive one morning summary for landing pages and pricing pages. An agency can batch client site checks before a weekly report. A product team can keep failed release checks immediate while successful runs stay in a digest.

RenderLog treats notifications as part of the product instead of a side channel. Each result has status, history, context and a notification path that matches how the team works.

Alert or digest?

Use an immediate alert when a person should stop what they are doing and inspect the run. Use a daily digest when the team needs visibility but the result can wait until the next review window.

The distinction keeps visual monitoring tied to the right review rhythm. A failed checkout check is interruption-worthy. A stable homepage check, a client site archive or a weekly documentation sweep usually belongs in a digest unless it breaks a baseline.

  • Immediate alert: failed run, missing selector, login wall or baseline mismatch on a critical page.
  • Daily digest: successful scheduled checks, low-risk pages and routine client reporting.
  • No notification: experiments, intentionally changing pages or checks without an owner.

Set the first notification rhythm

Keep launch-critical Check Suites on immediate alerts until the team has approved a few clean runs. Move low-risk successful runs into a daily digest when a short summary is enough.

The goal is not to hide problems. It is to match the message to the decision: urgent failures should interrupt the team, while stable recurring checks should create a readable operating rhythm.

Related links

API docs

FAQ

When should a check send an immediate alert?
Use immediate alerts for failed release checks, missing selectors, login walls and pages that no longer match their baseline.
When is a daily digest better?
Use a daily digest for stable scheduled checks where the team needs a compact summary instead of an interruption after every run.