Automated UiPath Queue Backlog Alerts
Every hour, WebRun opens UiPath Orchestrator, reads the pending, in-progress, and exception counts on each queue, compares the backlog against the same hour on previous days, sends the automation owner an alert on Telegram when a queue is growing faster than it is being worked, and posts the hourly queue position to Slack.
How do I know when a UiPath work queue is backing up?
WebRun reads your UiPath Orchestrator queues every hour, capturing pending, in-progress, and exception counts and comparing them against previous days. It alerts the automation owner on Telegram when a backlog grows for three consecutive checks, and posts the hourly queue position to Slack for the wider team.
- A growing backlog is flagged within an hour, not at end of day
- Alerts only fire on real growth, so the channel stays trustworthy
- The oldest pending item's age makes SLA risk visible immediately
Built for RPA teams · automation centres of excellence · shared service centres · operations managers
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
cloud.uipath.comin a real browser with your saved login - no setup, no API keys. -
1
UiPath - read queue backlog and exceptions
uipath.com
WebRun opens UiPath to read queue backlog and exceptions. - Open UiPath Orchestrator and go to Queues
- Read the new, in-progress, failed, and retried counts for each queue
- Compare the pending count against the same hour on previous days
- Flag any queue where the pending count has grown for three consecutive checks or where exceptions crossed your threshold
Done when Every queue has a current count and a growth direction.
-
2
Telegram - alert on a growing backlog
telegram.org
WebRun opens Telegram to alert on a growing backlog. - Send the automation owner an alert on Telegram for each flagged queue
- Say the queue name, the pending count, the growth over the last three checks, and the exception count
- Include the oldest pending item's age so the SLA risk is obvious
- Stay quiet on hours where every queue is inside its normal range
Done when The automation owner has been alerted about every backing-up queue.
-
3
Slack - post the hourly queue position
slack.com
WebRun opens Slack to post the hourly queue position. - Post the hourly queue position to your automation channel in Slack
- List each queue with its pending, in-progress, and exception counts
- Mark queues that are shrinking, holding steady, or growing
- Keep the format identical each hour so the trend is readable at a glance
Done when The automation channel has the current queue position in Slack.
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
Can it start jobs or add robots to clear the backlog?
No. WebRun only reads Orchestrator. It never starts a job, retries a queue item, changes a trigger, or allocates a robot, so scaling up stays a decision your automation team makes.
Will it alert me every single hour?
No. Telegram alerts only fire when a queue has grown for three consecutive checks or exceptions crossed your threshold. The routine hourly position goes to Slack, where it is easy to ignore.
Does it retry failed queue items?
No. Failed and retried items are counted and reported. Retrying an item, marking it as reviewed, or deleting it is always done by a person in Orchestrator.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.