Keep your 115 download queue from quietly stalling
Every hour, WebRun signs in to 115, reads your offline download queue, and works out which tasks finished, which are stuck part way, and which failed outright. It logs every status change to Google Sheets and posts the failures to Microsoft Teams with the task name.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I know when a 115 offline download task has failed?
Every hour WebRun signs in to 115, reads your offline download queue, and notes which tasks finished, which stalled, and which failed. It logs each status change to Google Sheets and posts the failures to Microsoft Teams, so a dead link gets re-added in an hour rather than a week.
- Failed tasks surface within the hour instead of days later
- Every task carries a dated status history in one sheet
- The team channel stays quiet when the queue is healthy
Built for media archivists · research teams · small studios · anyone running large download queues
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
115.comin a real browser with your saved login - no setup, no API keys. -
1
115 - read the download queue
115.com
WebRun opens 115 to read the download queue. - Sign in to 115 and open your offline download task list
- Capture the task name, its status, its progress, and the destination folder
- Compare each task against the status recorded on the previous run
- Mark a task as stalled when its progress has not moved since the last check
Done when Every task in the queue has a current status and a comparison against the last run.
-
2
Google Sheets - log each task status
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log each task status. - Append a dated row per task to your download log in Google Sheets
- Record the task name, status, progress, destination folder, and hours in the queue
- Update the row for a task that finished so the sheet shows the completion time
- Keep the history so you can see which sources fail most often
Done when The sheet holds one dated row per task with its current status.
-
3
Microsoft Teams - flag the failed tasks
microsoft.com How to Automate Microsoft Teams
WebRun opens Microsoft Teams to flag the failed tasks. - Post failed and stalled tasks to your team channel in Microsoft Teams
- Name each task and say how long it has been sitting without progress
- Stay quiet on the hours where everything is moving normally
- Add the count of tasks still running and how many finished since the last post
Done when Whoever queued the downloads knows which tasks need re-adding.
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 delete or retry tasks on its own?
No. WebRun reads the queue and reports. Removing a dead task or re-adding a link stays your call, so nothing in your storage is changed by a run.
How does it tell stalled from slow?
It compares each task's progress against the value it recorded an hour earlier. A task that has not moved between two checks is reported as stalled, not failed.
Does it download or open any files?
No. WebRun reads task names and statuses only. It never opens, moves, or downloads the files themselves, and file uploads are blocked by the run policy.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.