Question
Closed · Answered

If I limit an automation to three runs, does a failed run count toward the limit?

Hovhannes Vktarget

Before a page launch, I'd like Buda to check it at regular intervals and stop once I have three usable check reports.

The docs mention a maximum run count, but I'm not sure whether it counts attempts or successful runs. Does a failed or skipped run use up one of those slots? How would you configure a task where the goal is three completed reports?

Report
Kelly
Team

Max Runs counts scheduled attempts, not “successful reports.” A failed automatic run usually still uses a slot. Some skipped ticks also advance the counter. Manual Run now does not count toward Max Runs.

*Local demo / Diagram · Cap ≠ three good reports*

So what should you set for “three usable reports”?

  • Do not set Max Runs = 3 if you need three *completed* check reports — one failure would burn a slot.
  • Prefer unlimited (leave Max Runs empty) or a higher buffer, and put the success rule in the prompt, for example:
Keep checking on the schedule. After 3 completed check reports are saved, stop and disable further runs. Failed attempts do not count as completed reports.
  • Watch Automations → history: statuses include Completed, Failed, and Skipped — use Completed as your “usable” count.

How to verify

  • Trigger a run that fails on purpose (or review a past failure): run count moves even though there is no usable report.
  • Manual Run now leaves the Max Runs counter unchanged.
  • Your prompt stops after three Completed reports even if Max Runs is higher/unlimited.

Boundaries

  • Max Runs is a safety cap on how often the schedule may fire, not a quality gate.
  • If a pinned session is waiting for input, that tick may be skipped and still advance the schedule — clear blockers so you don’t burn attempts.
Report

Your reply

Sign in to join the discussion. Reading is always open; you only need an account to post.

Sign in