TechniquecurrentRunning agents

Flip an automation live in the session that proved the dry run

A proven dry run plus 'flip it on later' left my pipelines half-live.

SymptomYour job list or registry shows a job as live, but its recent runs logged dry-mode output.

Every new job I build that writes to an outside system (Salesforce, Slack, Notion, a published page) starts dry, behind one explicit live flag. That part worked, but the handoff after it didn't.

A dry run and a canary proved the path, and the flip became my terminal step for later.

Later turned into never often enough that proven pipelines sat half-live.

A job looked finished in its build notes and ran dry every night. Now the flip happens in the session that proved the path, with me running the gated command there. One dry run is enough for a deterministic job, and I hold only for a real prerequisite.

  • Code that hasn't landed yet.
  • A missing credential.
  • A send to people outside the team.

Two records keep it honest. Each job's actual mode sits in a registry that a daily check reads against its intent. And a dry run that mutates any state says so, because a dry run that advances a cursor is not dry.

Check your setup read-only

List your scheduled jobs that reach an outside system. Compare the live or dry flag in each loaded job's command line with the mode in your job registry. A flag can sit one hop away, in a wrapper script the command calls. Follow that hop before counting a mismatch. Any mismatch that remains is a gap.

Passes ifEvery job that reaches an outside system runs in the mode the registry records for it.

Access needed:schedulerlocal-config

If it fails: changes to make later (not part of the check)
  1. 01Default every new external writer to dry, behind one explicit live flag.
  2. 02Flip the job live in the same session once 1 dry run and 1 canary pass. Do not wait for a multi-night soak or a clean week. Do 2 dry runs if a model runs inside the job. Compare token use and output counts before the flip.
  3. 03File a ticket if the flip can't happen in that session. Put the exact commands and the verification query in the ticket.
  4. 04Make a dry run state any write in its help text and its digest. The writes are a cursor, a registry row or a staging post.
Applies ifYour scheduler holds a job that writes to a CRM, a chat tool or a published page.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.