3a4215aa78
When the Telegram Bot API rejects a sendDocument/sendPhoto/etc by URL (e.g. "wrong type of the web page content" or "failed to get HTTP URL content"), the entire reply was lost because the error propagated immediately via `?` with no fallback. Now when any send-media-by-URL call fails, the channel logs a warning and falls back to sending the URL as a plain text link. This ensures the user always receives the agent's response, even when Telegram can't fetch the linked content. Also makes `api_base` configurable via `with_api_base()` for local Bot API server support and testability. |
||
|---|---|---|
| .. | ||
| agent_e2e.rs | ||
| agent_loop_robustness.rs | ||
| channel_routing.rs | ||
| config_persistence.rs | ||
| dockerignore_test.rs | ||
| memory_comparison.rs | ||
| memory_restart.rs | ||
| otel_dependency_feature_regression.rs | ||
| provider_resolution.rs | ||
| provider_schema.rs | ||
| reply_target_field_regression.rs | ||
| telegram_attachment_fallback.rs | ||
| whatsapp_webhook_security.rs | ||