"My post says it published but nothing arrived"
Walk through these in order — the cause is almost always one of them:
- Is the group attached to the right category? Posts only fan out to groups attached to the post's own category. If you switched categories before publishing, the post may have gone somewhere else.
- Is the group switched on? Open Groups, find the row, and check the Auto-Publish switch. A disabled group is excluded from scheduled and bulk publishes.
- Is the platform still connected? Open Settings → Integrations and check the platform card. A red status badge or Not Configured means the connection has dropped.
- Did the platform itself reject the post? Each platform has its own rules — see the platform-specific sections below.
Telegram — common reasons it fails
- Bot is not a channel admin. Re-open the channel, go to Administrators, confirm your bot is in the list with permission to post messages.
- Wrong channel ID. The Add Group dialog validates the format inline. For private channels, only the numeric
-100XXXXXXXXXXform works —@usernameonly works for public channels. - Bot token is wrong or revoked. If you regenerated the token in BotFather, the old one stops working. Save the new token in Settings → Integrations → Telegram.
- You changed the bot. If you swap the bot token in Settings, you must add the new bot to every channel as an admin — the old bot's admin rights do not transfer.
WhatsApp — common reasons it fails
- Channel status is red, yellow, or shows an error. Open Settings → Integrations → WhatsApp → Manage Channels and check the status badges. Anything that is not Connected means the session is not usable.
- Linked device was removed. If you tap Log out on the linked device list in your phone's WhatsApp, the session is killed. Reconnect by scanning a fresh QR.
- Group ID changed. If you re-created the WhatsApp group on your phone, its underlying ID changes. Edit the Afflow group and use Re-sync from WhatsApp to pick the new group.
- You are no longer in the group. If you left or were removed, the linked device cannot post there anymore.
Facebook — common reasons it fails
- Status badge says Expired. Facebook access tokens expire periodically. Click Connect Facebook Page in Settings to re-run the OAuth flow.
- Status badge says Revoked. Someone removed Afflow from the connected apps in your Facebook account. Re-authorise from Settings.
- You lost admin on the page. If your role on the Facebook page changes, posting can stop working even though the connection still looks active. Check your role inside Facebook itself.
- You did not grant page permissions during OAuth. Re-run the connect flow and make sure you do not deselect any pages on the permissions screen.
Instagram — common reasons it fails
- The account is not a Business Account. Instagram's publishing API only works for Business Accounts. Convert it inside Instagram and re-run the OAuth.
- The account is not linked to a Facebook page. Instagram publishing is gated through Facebook — without a linked page, the account will not appear in the connect dialog.
- The Facebook side disconnected. Instagram piggybacks on the Facebook connection, so if Facebook expires or is revoked, Instagram stops too. Reconnect Facebook first.
"The conversion shows up but is not attributed to a post"
Tracking only attaches when both the category has tracking enabled and the destination group has a Tracking ID configured. If either is missing, the post still publishes — but with the marketplace's default affiliate link, so the conversion will not link back to a specific post in Reports → Post Tracking. Set the group's Tracking ID in the edit dialog, and turn on tracking in Posts → Settings → Tracking for the category.
"I cannot add another group"
Your subscription plan caps how many groups you can have in total across all platforms. When you hit the cap, the Add Group button is disabled and a tooltip shows your plan limit. Either delete a group you no longer use, or upgrade your plan from Settings → Subscription.
"Posts arrive in the wrong language"
Each group has its own Language setting. When a post is sent to a group whose language differs from the category's content language, Afflow translates the copy automatically. If the wrong language is going out, edit the group and make sure its Language matches the audience that actually reads it.