Catch the bots that stopped running your flows
Every morning, WebRun opens airSlate, goes through the bots inside your live Flows, finds the ones that failed or never fired since yesterday, posts Microsoft Teams a list naming the Flow and the step it stalled at, and pings Telegram when documents are waiting behind a stuck Flow.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I find out when an airSlate bot fails inside a Flow?
WebRun opens airSlate every morning, reads the bots inside your live Flows, and finds the ones that failed or never fired. It posts Microsoft Teams a list naming each Flow and the step it stalled at, and pings Telegram when documents are waiting, so a stuck Flow is fixed before anyone complains.
- You learn a Flow is stuck and at which step, before users report it
- Bots that never fired are caught alongside outright errors
- Documents waiting behind a failure are counted and prioritised
Built for operations admins · document automation teams · finance operations · HR operations
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
airslate.comin a real browser with your saved login - no setup, no API keys. -
1
airSlate - check bot runs across Flows
airslate.com
WebRun opens airSlate to check bot runs across Flows. - Open your Workspace and list the Flows that are live
- For each Flow, read its bots and the outcome of their most recent runs
- Capture failures and bots that should have fired but did not, noting the step and the documents waiting behind it
Done when Every live Flow has its bot outcomes read, with failures and silent bots identified by step.
-
2
Microsoft Teams - post the failures by Flow
microsoft.com How to Automate Microsoft Teams
WebRun opens Microsoft Teams to post the failures by Flow. - Post a list to your operations channel grouped by Flow, failures first
- Give the bot name, the step it stopped at, the error text shown, and when it last ran successfully
- Note how many documents are held up behind each stuck Flow so priority is obvious
Done when The operations channel has today's list of failed and silent bots with the affected step for each.
-
3
Telegram - ping when a Flow is stuck
telegram.org How to Automate Telegram
WebRun opens Telegram to ping when a Flow is stuck. - Send a short alert when a Flow has documents waiting behind a failed bot
- Name the Flow, the step, and the number of documents held up
- Skip the message entirely on a clean morning so the alert stays meaningful
Done when Any Flow holding documents behind a failed bot has triggered a named Telegram alert.
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 restart or edit a bot on its own?
No. WebRun reads the run history and reports. Rerunning a bot, fixing a step, or changing a Flow stays with your admin, so nothing in airSlate is altered by this workflow.
Does it catch a bot that simply never fired?
Yes. It compares each bot's last successful run against how often that Flow normally moves, so a bot sitting silent shows up next to the ones that returned an error.
Will it send documents or contact signers?
Never. The only messages it sends are the internal summary in Microsoft Teams and the alert in Telegram. No document is sent and no signer is contacted.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.