← Back to Programming and automationOpenClaw automations
Reliable automation patterns
Reliable automation is not “runs sometimes.” It is observable, restartable, and honest about whether the artifact actually landed.
Design for realityAssume stalls, tool flakes, and wrong-context mistakes will happen. Good automation plans for that up front.
Core patterns
The reliability rules worth keeping
Receipts
Success should be proven with files, URLs, outputs, or logs — not just “done” text.
False green defense
Do not confuse in-progress labels with artifact completion.
Recovery design
Know the restart path before the workflow stalls.
Examples
What this looks like in practice
Content pipelineEach stage should leave a named artifact, not just a claim that “research happened.”
QA workflowScreenshots, reports, or diffs are stronger than status summaries.
Watchdog flowThe workflow should know whether to retry, reroute, or restart when nothing moved.
Open deeper reference links for this page