Failover across AI accounts, without doing a task twice
- Problem
- The Discord bot went silent from 2:57 to 4:40 AM when one account hit its 5-hour limit. In 30 days of transcripts, 23 of 29 API errors were that limit.
- Approach
- Every kind of work has a route in one config file naming its first account and what to try next. A job hands over only if it was refused before any tool call; after a tool call it is never redone elsewhere. At most one switch in 15 minutes, and a switch back only after 3 quiet minutes.
- Result
- Job routes fall back to a second model instead of stopping, and nothing runs twice.





