Delivery log

The delivery log of a chat with statuses, the per-post pipeline trace, and how edits and deletions are kept in sync.

Processed messages in the chat settings (the Data Sources block) is the delivery log, the chat's history: every post the bot received from the chat's sources, what happened to it and why. It is the first place to look when "nothing arrives" or "the post looks wrong".

The history of a chat with its filters.
The history of a chat with its filters.

The list

One row per post: the source, the time, a short preview and the status:

  • Delivered — sent to the chat; Open post jumps to the message. On rows that were not delivered, Open in channel opens the post in the source.
  • Filtered — dropped by a filter; the row names the rule that matched.
  • Failed — Telegram or the source refused; the row keeps the error details.
  • Awaiting publication — parked by deferred posting or the delivery window, not yet sent.
  • Skipped / Partial — the post was not sent for another reason, or only part of an album went through; the row explains.

Filter the list by status, by date range, by source and by source type. The number of active filters is shown on the filter button; Reset clears them (and Apply applies the choice).

One post in detail

Tap a row to expand it. The row shows the final text as it was sent, the buttons, the attachments, and two snapshots — the source settings and the chat settings at the moment of delivery. Snapshots are what make old rows readable: if you change a template today, yesterday's rows still show which template produced them.

Below that sits the pipeline trace — what was applied to the post, one block per step:

  • Recipient filters — passed, or dropped by which rule.
  • Duplicate check — a duplicate found, or none (shown for posts dropped as a duplicate).
  • Category detection — only with smart routing: which category was picked and with what confidence; the step also shows how long it took.
  • Delivery — the result and the way it went out (bot or account); for a failed post, the error.

Replacements, AI processing and translation are not separate steps in this trace: their result is the final text above. On a phone the steps stack vertically; on a wide screen they run left to right with arrows between them. The trace is recorded for filtered posts as well, so "why was it dropped" is answered by the same block as "how was it delivered".

Events log

Events Log in the Management section of the chat settings is a feed of what happened to posts: what was not delivered (filtered out, filtered out by AI, a clone that was already published) and how clones updated posts already published (media added or replaced, description added or replaced, see Similar posts).

Tap an event to open its card: a media preview, the text, the reason, the processing trace step by step, and links to the post in the source and to the published copy.

Edits and deletions

When a source edits or deletes a message, Routify can repeat the change in the chat — see Syncing edits and deletions. To do that it remembers which delivered message corresponds to which source message. The memory is kept for 72 hours after delivery — longer than Telegram's own 48-hour window for editing a message — and survives restarts of the service. For a source the bot reads, deletions are tracked for 48 hours. Older edits and deletions are not propagated.

Copying the past

A source with New messages starts from the moment it is added — delivery does not look back. A source's earlier posts can be copied separately: the Old messages (history) forwarding type when adding it, or Copy old messages in the source card, when your account reads the source — see Copying old messages. To check the pipeline on a single post, use Send latest post in the source card.

Retention

The log keeps the last 500 events of a chat and no longer than 14 days; older rows disappear on their own. Unlink chat in the chat settings removes the chat from your list, but its sources and settings are kept and the chat can be linked back; see Security for what else is stored and how to remove it.

Set up your first forward today

Every post you copy by hand is time the bot could save you. Open the bot, send a public channel’s link and pick where to forward it: the first messages arrive within minutes.

Open @RoutifyBot