SkufosaurRU
Menu

Recipe / Retries

Give the retry loop an exit

Decide when an agent should stop, retry or hand a decision back to the operator.

95%

Decide when an agent should stop, retry or hand a decision back to the operator.

Sections and scope

Bounded workflows with repeatable actions and a defined acceptance check.

This is a proposed policy with synthetic cases. It has not been benchmarked and does not control running processes.

Quick check

Set the acceptance check, retry budget and handoff conditions before running the agent.

Download the test script · node check-stop-policy.mjs

Five cases cover success, handoff, budget exhaustion, a justified retry and a repeated failure.

Synthetic inputs. This tests the rule and makes no model or cost claims.

Define the exit before starting

  • Stop successfully when the acceptance check passes.
  • Stop with a partial result when the budget runs out.
  • Retry when the error is plausibly transient and an attempt remains.
  • Hand off when progress requires permission, missing data or a decision from the operator.

A fifth trip around the roundabout is still the same roundabout.

Check the handoff

Try one temporary timeout and one denied permission. The first can justify a bounded retry. The second should report the missing permission and preserve completed work. Report what passed, what remains and which input would let the work resume.

Sources and origin

  • Skufosaur editorial method

    Proposed stop conditions checked on synthetic inputs. No model performance or cost measurements.