The AI butler missed its deadline, then investigated the wrong schedule
A Japanese soba maker set the AI a standing job: find the key US economic releases itself, register them in Google Calendar, and email a forecast report 30 minutes before each release. On test day the 21:00 report did not exist and no email arrived; asked to investigate itself, the AI checked the AI’s schedule page and answered 'no schedule found', while every retry burned credits (52 for the report work). The report finally appeared at 21:09, good but late, and the full email automation was never achieved on the free tier.
How it works
- Owner designs the chain with AI: The AI finds releases, calendars them, researches and emails a report 30 minutes ahead
- Repeated setup and fix rounds consume credits each time
- On the day, 21:00 passes with no report and no email
- The AI investigates itself by checking the wrong system's schedule and finds nothing
- Report finally lands at 21:09, after the deadline but before the 21:30 release
- Owner concludes stable full automation was not possible within the free allowance
Why it’s worth knowing
Debugging was delegated too, and the agent investigated a different product's schedule, answering 'you have no schedule' about the job it was itself supposed to run.
Where it’s from
Summarized from a public post on note.com. See the original ↗