Automated JW Player Failed Upload Alerts
Every hour, WebRun opens JW Player, checks the media added since the last run, finds anything that failed processing or has been stuck too long, records it in a Google Sheet with the upload time and any error shown, and adds a hold to the Google Calendar slot the video was meant to fill.
How do I catch video uploads that failed to process?
Every hour, WebRun opens JW Player, checks the media added since the last run, and finds anything that failed processing or has been stuck too long. It logs each one in a Google Sheet with the upload time and error, then places a hold on the Google Calendar publishing slot, so a dead embed is never shared.
- A file that never processed is known within the hour, not at publish time
- Every failure is logged with its error, so repeat offenders are obvious
- The publishing slot carries a hold before anyone shares a broken embed
Built for video producers · media teams · publishers · marketing content teams
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
dashboard.jwplayer.comin a real browser with your saved login - no setup, no API keys. -
1
JW Player - find media that never processed
jwplayer.com
WebRun opens JW Player to find media that never processed. - Open JW Player and go to your media library
- Read the processing status of every item added since the last run
- Flag anything marked failed, and anything still processing longer than your patience threshold
- Capture the title, the upload time, the duration if known, and any error text shown
- Check whether the item sits in a playlist that is already live
- Read only. Never delete, re-upload, or unpublish media
Done when Every failed or stuck upload from this hour is captured with its status.
-
2
Google Sheets - log the failed uploads
google.com
WebRun opens Google Sheets to log the failed uploads. - Append one row per failed or stuck item with the time WebRun found it
- Record the title, the upload time, the status, the error text, and whether it is in a live playlist
- Mark rows resolved when the item shows as ready on a later run
- Keep the history so a repeatedly failing source file is easy to see
Done when The sheet holds every unprocessed upload with its current status.
-
3
Google Calendar - hold the publishing slot
calendar.google.com
WebRun opens Google Calendar to hold the publishing slot. - Find the publishing slot the video was scheduled to fill
- Add a hold on that slot naming the title and the processing problem
- Leave existing events alone. Never cancel or notify external guests
Done when Every affected publishing slot carries a visible hold.
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
Will it re-upload or delete the broken media?
No. WebRun reads processing status and logs it. Deleting the failed item and uploading the file again stays with your team, so no master file is removed by an automation.
How long before a stuck upload is flagged?
You set the threshold, commonly 30 minutes past the usual processing time for that file length. Anything marked failed is reported on the very next hourly run.
Does it tell anyone outside the team?
No. The log is your own Google Sheet and the calendar hold is on your internal publishing calendar. WebRun never emails a client, cancels an event, or notifies external guests.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.