# Upgrade Guide — vNEXT

<!-- bump: patch -->

## What Changed

Fixed a critical gap in the Telegram lifeline's API call handling. The lifeline's `apiCall` method had no handling for HTTP 429 (Too Many Requests) responses from the Telegram API. When Telegram rate-limited the bot, the lifeline threw a generic error, but callers kept sending more messages — each hitting the rate limit again, generating 13,700+ error lines in stderr and creating a cascade of failed requests.

The fix adds the same retry_after-aware handling that TelegramAdapter already has:
- Parse the `retry_after` field from Telegram's 429 response
- Wait the specified duration before retrying
- Retry up to 3 times with proper backoff
- Throw a clear error after max retries instead of cascading

This was the root cause of massive stderr spam during message bursts (e.g., server restart notifications, queue ack confirmations).

## What to Tell Your User

- **Rate limit handling**: "My emergency communication channel is now smarter about Telegram's rate limits. If Telegram asks me to slow down, I'll wait and retry instead of flooding error logs. This means more reliable message delivery during busy periods."

## Summary of New Capabilities

| Capability | How to Use |
|-----------|-----------|
| Lifeline 429 rate-limit handling | Automatic — retries with backoff on Telegram rate limits |
