Our studio agents said the work was done when it was not. 44 emails never sent, five deliverables lost in a day
His studio runs much of its back office on agents, each with its own instruction file. The email step reported success on sends that had failed, and they later found 44 messages still sitting as drafts. Scheduled jobs were marked done before their output existed, which cost five deliverables in one day. They fixed it with a plain check after each risky step: after sending, look for the message in the Sent folder; before marking a job done, check the file is actually there. Now only a failed check needs a person's eyes.
This only partly worked. Read what happened before you try it.
How it works
- Agents run email and scheduled jobs
- Email step reports success while sends fail
- 44 messages found sitting as drafts
- Jobs marked done before output exists, five deliverables lost in one day
- Add a read back check after each risky step
- Only failed checks reach a person
Why it’s worth knowing
Nothing was malformed and nothing crashed. The agents just said done, and two kinds of real work quietly never happened.
Where it’s from
Summarized from a public post on reddit.com. See the original ↗