Channel troubleshooting.
It says verified but nothing arrives. No brief was generated. Both channels fire at once. Each of these has a one-line cause — and none of them is the thing people first assume.
Five problems account for nearly every channel support ticket. Work down the list — the first two are the answer most of the time, and neither is a fault.
It says verified but nothing arrives
The channel row shows a green Verified badge. No brief has ever landed.
Slack and Discord channels are marked verified the moment you paste the webhook URL. Nothing calls it to check. A typo, a stale webhook, or one that was deleted on the platform gives you exactly the same green badge as a working one.
The fix is one click: hit Test on that channel row.
- The sample brief arrives → the channel is genuinely fine, and your problem is elsewhere on this page.
- It fails → you get the platform's error inline, in red. Delete the channel, re-copy the webhook URL from Slack or Discord, and add it again.
No brief was generated this morning
Not “it wasn't delivered” — the app itself says there's no brief for today.
A brand with no connected delivery channel does not get a brief generated at all. We don't spend your credits writing something nobody asked to receive. So the first three things to check are all about channels:
- Is a channel connected on this brand? Channels are per brand. A brand you added last week has none until you add one.
- Is your only channel paused? A paused channel doesn't count as connected. Pausing your last channel stops the brief being generated, not merely delivered — you come back to a hole in your archive.
- Has the hour passed yet in the timezone you saved?
You can always press Generate today's brief on the Daily Brief page to produce one on the spot. How the schedule works → · Every other empty-brief cause →
Both channels send at the same time
You set Telegram to 9am and Slack to 6pm. Both now arrive at 6pm.
That's not a bug, though it is a surprise. The send time belongs to the brand, not to the channel. There is one brief per brand per day, and it goes to every connected channel at the same moment — so the last hour you saved becomes the hour for all of them. The Telegram row may still display 9am; believe the last hour you saved, not the row.
Different brands can absolutely have different times — that's the intended way to run several clients. What you can't do is send one brand's brief to two channels at two different hours. The full explanation →
Telegram still says pending
You opened the bot and pressed Start, and the row still shows Pending with no Test button.
The channel row doesn't update itself. The bot links your chat the instant you press Start, but the page you're looking at was rendered before that happened. Reload it and the row flips to Verified, with a Test button.
If it's still pending after a reload:
- Did you actually press Start? Opening the chat isn't enough — the bot needs the Start command to receive your link.
- Did you use the button in the app? The Connect Telegram button carries a one-time link tied to that channel row. Searching for the bot by name and messaging it won't connect anything; the bot will reply telling you as much.
- Start again from a fresh link. Delete the pending channel, add Telegram again, and use the new Connect button.
Reading the error on a failed send
Open Delivery history under the channel list — your last 20 sends. Any row marked Failed carries a warning icon; hover it and you get the raw error the platform returned.
| What you see | What it usually means |
|---|---|
HTTP 404 | The webhook no longer exists — it was deleted, or the URL has a typo. Re-create it and re-add the channel. |
HTTP 403 | The webhook exists but you're not allowed to post to it — the app was removed, or the channel was archived or made private. |
| A Telegram error about the chat | You blocked the bot or deleted the chat. Delete the channel and connect Telegram again. |
The morning delivery runs once. If your channel rejects it, ScoutRival logs the failure and moves on — no retry, no email, no in-app alert. The brief was still generated and is in the app; only the delivery died. The delivery history is the only place this is ever reported, so it's the first thing to open on a quiet morning.
I need to change the hour or the webhook
There is no Edit on a channel. Delete it and add it again with the new settings — your delivery history is kept. Re-adding also rewrites the brand's send time to the hour you pick, which is usually what you were trying to do anyway. Changing the hour →
A post arrived cut off
Almost always Slack. Slack caps the text in a single section block, so a suggested post longer than roughly 2,900 characters is truncated there rather than continued. Telegram and Discord split long content across messages instead, and lose nothing.
The complete text is always in the app. If long drafts are normal for you, add Telegram or Discord alongside Slack — the brief goes to every connected channel. Per-platform formats and limits →