Atlassian consultant and Forge developer at LeanZero. We do Data Center to Cloud migrations and build Forge apps, and I write up what I learn at leanzero.net.
I started LeanZero because I saw an industry full of process-heavy companies charging enterprise prices for work that could be done faster, leaner, more honestly. The Atlassian ecosystem shouldn't need a small army and a six-figure budget to get things done right. I hold Atlassian Certified Administration Expert status: ACP-120, ACP-220, ACP-420 and ACP-520, covering Jira, Confluence, Jira Service Management and cloud org admin. Other certs: PSM I, SSM, AWS Cloud Practitioner. I specialize in Forge app development and run an AI-powered agentic workflow I built myself, so I can build across stacks without a dozen specialists. Cloud migrations are my bread and butter, from small teams to orgs with tens of thousands of users. The MCP Doc Processor came from a simple frustration: nothing on the market fit, so I built it. I'm not selling magic pixie dust. I'll tell you honestly what's possible, what's hard, and what you actually need. If you don't need to pay me, I'll tell you that too.
Markdown supported · ⌘↵ to post
What stood out to me here is the focus on silent failures rather than obvious crashes. An automation can look perfectly healthy from its logs while doing nothing useful, which is a much harder problem to catch in production. This is especially relevant when building AI powered workflows at Oglas AI we’ve found that observability, validation, and reliable failure handling matter just as much as the automation itself.
Mihai_LeanZero
Mike Dabydeen
I'd keep your closing check and move where it counts: read the destination, not a ledger the agent writes. That ledger is still the agent's account of what it did. If a post is accepted by the API and then held by a spam filter, or the process dies between writing the ledger line and the actual submit, the ledger and the platform disagree, and the ledger wins because it's the one you're reading. The version I'd trust reads the published output from the target system after a short delay and compares it with what the run claimed.
One caution from the other direction: some platform APIs lag their own rendered pages. Right after a successful post, the API can still report nothing new. A check that reads too early and retries on "missing" turns a success into a duplicate. So the ground-truth read wants a delay, and a rule that a missing post gets reported, not reposted.
Smaller point on the lock. The 90-minute age break fixes the permanent wedge, but a recycled PID still skips every tick until the lock ages out, which at five-minute ticks is up to 18 lost runs. Writing the process start time next to the PID (ps -o lstart= -p "$PID" works on macOS) lets the liveness check confirm it's the same process rather than any live one, and the age break becomes a backstop instead of the main defence.