How delivery works

The pipeline

1. A supported link appears in a message posted to the group.
2. The bot reacts with ⏳ on that message, then looks the link up in the shared media cache (50M+ files across our bots).
3. Cache hit — the file is already there: it is delivered in a couple of seconds, at no cost against the group's plan.
4. Cache miss — on a paid plan the bot downloads the media fresh, subject to the plan's weekly traffic, file-size and resolution limits; on the free plan nothing is downloaded and the link is skipped. See Cache vs. fresh download.
5. Delivery replies to the original message with the photo, video or audio, respecting the chat's caption/progress/emoji settings, then the reaction becomes ✅ on success or 😢 on failure.
6. Continue elsewhere — two buttons under the delivered file hop to @download_it_bot with the same link, to pick another format or grab just the audio.

What can make delivery skip or fail

• The link is not from a supported service.
• The group is on the free plan and the link is not yet cached.
• The group's weekly traffic is used up, or the file exceeds the plan's size cap.
• Admins-only mode is on and the message came from a non-admin.
• The source itself is unavailable — removed, private, or geo-restricted.

Every one of these shows up with its own status in Statistics and logs, so you don't have to guess why nothing arrived.