Automated Brightcove Failed Encode Alerts
Every hour, WebRun opens Brightcove Video Cloud, checks recently ingested videos for stuck or failed encodes, posts a status alert to Slack, and pings Telegram directly when a failed video's publish deadline is under two hours away.
How do I catch a failed Brightcove video encode before it misses its deadline?
WebRun checks Brightcove Video Cloud every hour for videos stuck in processing or marked as a failed transcode, comparing each against its scheduled publish time. It posts a status alert to Slack for the team, and pings Telegram directly when a failed video's publish deadline is under two hours away, so a stuck upload never quietly blows a deadline.
- Stuck encodes get caught within the hour, not after a missed deadline
- The team only gets pinged directly when a deadline is truly at risk
- No manual dashboard checking required
Built for media companies · broadcasters · video operations teams · publishers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
studio.brightcove.comin a real browser with your saved login - no setup, no API keys. -
1
Brightcove - check ingest and encode status
brightcove.com
WebRun opens Brightcove to check ingest and encode status. - Open Brightcove Video Cloud and check videos ingested in the last 24 hours
- Note any stuck in processing or marked as a failed transcode
- Compare against each video's scheduled publish time
Done when Every recent video has a current ingest and encode status.
-
2
Slack - post the status alert
slack.com
WebRun opens Slack to post the status alert. - Post a status alert listing any stuck or failed videos
- Include the video title and how long it's been stuck
- Post nothing when everything encoded cleanly
Done when The team knows the encode status of every recent upload.
-
3
Telegram - ping on deadline risk
telegram.org
WebRun opens Telegram to ping on deadline risk. - Send a direct ping only when a failed video's publish time is under 2 hours away
- Include the video title and error state
- Leave the fix itself to the video team
Done when Anyone with a deadline at risk has been pinged on Telegram.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it try to fix a failed encode?
No. WebRun only detects and reports the failure. Re-uploading or re-encoding the video is left to your video team.
Why does Telegram only ping sometimes?
It's reserved for videos whose publish time is under two hours away, so routine delays stay in Slack and only real deadline risk interrupts you directly.
What if every video encodes fine?
Then no alert posts. WebRun only speaks up when something is stuck or failed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.