Automated Alteryx Stuck Job Alerts
Every hour, WebRun opens your Alteryx job queue, reads which jobs are queued and which are running, compares every in-flight run against its own typical duration, and alerts your administrator in Microsoft Teams and Telegram when a job is stuck, blocking the queue, or running far longer than it should.
How do I find out when an Alteryx job is stuck in the queue?
Every hour, WebRun opens your Alteryx job queue, reads what is queued and what is running, and compares each run against its own typical duration. It alerts your administrator in Microsoft Teams and Telegram when a job is stuck or running far too long, before the afternoon schedule backs up.
- A blocking job is known within the hour, not at the end of the day
- Alerts are judged against each workflow's own history, so normal long jobs stay quiet
- One ping per incident rather than an hourly repeat while it is still running
Built for data engineers · analytics teams · BI administrators · IT 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
alteryx.comin a real browser with your saved login - no setup, no API keys. -
1
Alteryx - watch the running job queue
alteryx.com
WebRun opens Alteryx to watch the running job queue. - Sign in and open the job queue, listing everything currently running and everything still queued
- Record how long each running job has been going and which workflow and schedule it came from
- Compare each run with the typical duration for that workflow from previous runs
- Flag any job running more than twice its usual time, and any job queued past its scheduled start
- Note how many jobs are stacked behind the slowest one
- Read only. WebRun never cancels, restarts, or reschedules a job
Done when Every running and queued job has an elapsed time and a comparison against its usual duration.
-
2
Microsoft Teams - alert the administrator
microsoft.com
WebRun opens Microsoft Teams to alert the administrator. - Post to your data engineering channel when a job crosses the threshold
- Name the workflow, the schedule it belongs to, how long it has run, and its usual duration
- Say how many jobs are queued behind it, so the impact on the afternoon is obvious
- Stay silent on hours where every job is running normally
Done when The data channel knows within the hour which job is stuck and what is waiting behind it.
-
3
Telegram - send the on-call ping
telegram.org
WebRun opens Telegram to send the on-call ping. - Send a one-line ping to the on-call group for anything running more than three times its usual duration
- Include the workflow name and the elapsed time only, so it reads at a glance on a phone
- Send one ping per stuck job, not one per hourly check
- Keep it internal to your own group
Done when The on-call group has a single short ping for each genuinely stuck job.
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 cancel or restart the stuck job?
No. WebRun reads the queue and reports. Cancelling a long-running job can leave data half written, so that call stays with your administrator, who gets the elapsed time and the queue depth to decide with.
How does it know what is too long?
It compares each run with the same workflow's own history, so a job that normally takes two hours is not flagged at ninety minutes. The multiplier that triggers an alert is yours to set.
Will it ping every hour while a job is still stuck?
No. Each stuck job produces one Telegram ping, and the Teams post updates rather than repeating, so a long incident does not turn into hourly noise.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.