The Operations section shows every post from the source and what happened to it in each target: published, waiting in the queue, failed or filtered out — and why. Fix it right there: publish, retry or answer the bot’s question.
Cross-posting means many posts and many platforms, and sooner or later the question comes up: “where is that post?” The Operations section answers it without support: it shows every post from the source and what happened to it in each target, including posts removed by filters.
The reason is always clear — which filter fired, what error occurred, which decision you made. And you can fix things right there: publish a filtered post, retry after a failure, answer the bot’s question or cancel a post in the queue.
The section is available on the website and in the mini app. At the top — a 7-day summary: how many posts were received, published, filtered, how many errors and what is waiting in the queue.
Switch tabs, pick a single target or search by post text. In the All tab posts are listed in order of arrival, each with a link to the original in the source.
Under each post there is a line per target: published (with a link and the delay), queued, awaiting decision, error with the reason, filtered with the reason, or cancelled.
Publish — for a filtered post, Publish again — for an error, answer buttons — for the bot’s question, Cancel — for a post in the queue.
A filtered post no longer disappears silently. The reason is written in plain words: “Ad filter: erid label”, “Publication limit reached (100 of 100)”, “Repost — reposts are not published in this project”, “Target filter: only posts with photos are published”, “Required words missing”.
The filter got it wrong? Press Publish and the post goes to the target bypassing the rule that fired. The button is available for 24 hours after the post arrives, once per target. The current text goes out: if you already fixed the post in the source, the fixed version is published.
The button appears only where a retry can help: a platform or network failure after all automatic retries, restored permissions or a reconnected account, an AI error. If the platform rejected the content itself, there is no button — a retry would fail the same way.
When the bot asks what to do with a post (for example, the text exceeds the Max limit), you can answer not only in the bot but also in the Queue tab — with the same options: shorten, split into multiple, skip and more.
Each target keeps what was decided and where: “Shorten text — in the Telegram bot, 06:02”, “Without AI processing — on the website”, “Decision time expired”. You can see why a post came out the way it did.
The Errors tab holds network, permission, token, AI and platform failures. What a platform will never accept (for example, a video over its limit or a “Skip” decision) goes to Filtered with a reason instead of mixing with errors.
Open the project → Operations and find the post by text search or in the All tab. Each target shows a status: if the post was filtered, the Filtered tab shows which filter fired; if it failed, the Errors tab shows the reason.
Posts removed by project and target filters: the ad filter (with the rule that fired), an exhausted publication limit, reposts and posts with buttons when set to skip, the target content filter, forwarding percentage, the keyword filter, a scheduled pause, cases where the platform will not accept the post, and the “Skip” decision.
24 hours after the post arrives, one press per target. After that the button disappears, while the record with the reason stays. There is no button for posts the platform technically cannot accept (for example, a video over its limit) or for posts deleted in the source.
The button is shown only where a retry can help: a platform or network failure, permissions and tokens (after you restored them), an AI error. If the platform rejected the content itself or the post was deleted in the source, a retry will not help. After a manual publish the button does not come back for that target — if it fails too, contact support.
No. The limit is spent only on posts actually sent. Filtered posts do not take a place in the queue. When you press Publish, the limit is checked as for a normal publication.
No. Messages filtered out by group settings (forum topic, admins only, no replies) are not recorded in Operations — active chats produce thousands of them. Posts that arrive while the project is paused are not recorded either.
Yes. Cancel a single post or all of them with Cancel all in the Queue tab. Posts being published at that moment are not affected.
Posts are kept for 180 days. The section refreshes automatically every 30 seconds.
erid markers, hashtags, your own words, links, @mentions, phone numbers and emails — an ad post never reaches your targets, and Operations shows exactly which rule fired.
Learn moreA post waits in the queue for the time you set. Edit it in the source — targets get the corrected version. Delete it in Max — publishing is cancelled automatically.
Learn morePhotos, videos, albums, voice messages, documents — with formatting preserved. Polls go to OK natively and to other platforms as text with answer options. What a platform does not support, the bot adapts or asks you about.
Learn moreConnect the bot in 2 minutes. Free plan — no cards, no signup.
