Fallback provider may not start after a rate limit
A can appear ready to switch to a when the primary provider hits a daily limit. In this case, it did not switch. Telegram first showed a working status with , saying it was on retry 2 of 3 with 89 seconds left.
Then it showed a rate-limit message telling the user to wait and try again. The agent never used the . The itself seemed to work, and it also appeared in the when running `hermes fallback`.
The real issue is whether Hermes needs another setting before it will switch, or whether are handled as retries instead of fallback failures.
Key points
- The primary provider hit a daily rate limit.
- The agent retried and then showed a rate-limit message instead of switching.
- The appeared to be installed and visible through `hermes fallback`.
- A listed may still need extra setup or may not cover every failure type.
- Users should test real fallback behavior before relying on it for long automated tasks.