To understand why a bot did not publish an article, follow one article through the complete chain: source → theme → bot selection → schedule or review queue → generated post → social network. Stop at the first stage where the expected item is missing; changing later stages cannot repair an earlier detection or filter problem.
1. Confirm that the source contains the article#
Open the theme selected by the bot and search for the exact article. If it is absent, check the source first:
- an RSS item must be present in the configured feed;
- an SDK or crawler source needs an anonymously reachable canonical URL;
- a direct URL refresh needs a successful page response and usable metadata;
- the article date and language must fall within the theme's current filters.
For website sources, use Why is my web content not displayed?. For RSS, review how to add an RSS feed.
2. Check the bot configuration#
In Bots, open the relevant bot and verify:
- the bot is active and its company has an active pack;
- the selected brand, theme, and theme section are correct;
- every destination social account is connected and active;
- include and exclude terms, URL rules, tags, language, domain, and source filters allow this article;
- the consultation period, days, timezone, and frequency include the article's publication time;
- daily and per-account maximums have not been reached;
- deduplication, maximum reposts, and minimum posts before reposting do not exclude the article;
- the chosen message, title, description, image, comment, and alt-text sources exist for the article.
Also check whether the filtered result set is empty. After changing a source or filter, allow the configured refresh and consultation intervals to complete; repeated refreshes do not make an article eligible sooner. During a high-volume burst, daily limits, post distribution, deduplication, social-network rate limits, or anti-spam protections can defer or skip otherwise eligible items.
The current social bot form also controls immediate versus planned publication, review-queue placement, post-type distribution, hashtags, URL cleanup, Smart Image, and PublishGuard. Confirm whether the expected operating mode is automatic publication, planned publication, or manual validation. Review these fields instead of assuming that an active bot publishes every item in its theme.
3. Find the generated post#
If the article passed selection, look in Posts and in the reviewing queue when Put posts in reviewing queue is enabled. A generated post that is pending, quarantined, scheduled, or failed proves that detection and bot selection already succeeded; diagnose the later state rather than changing the feed.
- In the review queue, approve or correct the post according to your workflow.
- For PublishGuard quarantine, follow the quarantine review guide.
- For a scheduled post, verify the exact timezone and publication window.
- For a failed post, use the publication error guide.
4. Worked example#
Suppose an article appears in the bot's theme but no post is visible. The bot is active, yet its consultation window ended before the article timestamp: the failure is scheduling, not RSS ingestion. After correcting the window, wait for the next configured consultation. If a post then appears in the review queue, selection works; it will not reach the social network until a reviewer releases it.
5. Support checklist#
If the chain still breaks, send support the article URL, source type, theme and bot names, affected brand and destination account, article timestamp, bot timezone and consultation window, the stage where the item disappears, and the exact visible status or error. Remove private content and never send passwords, tokens, feed credentials, API keys, or authentication codes.