Automated Harness Deployment Failure Escalation
Every few minutes, WebRun opens Harness, checks pipeline deployments for a failure or an automatic rollback, posts the details to Telegram naming the service and environment, and texts the on call engineer through Twilio when the failure happened in production so a broken deployment gets attention before it affects customers.
How do I escalate failed production deployments from Harness fast?
WebRun checks Harness every few minutes for a pipeline deployment that failed or was automatically rolled back. It posts every failure to Telegram for the team, and texts the on call engineer through Twilio when the failure happened in production, so a broken deployment gets attention before it affects customers.
- Production deployment failures reach on call within minutes
- Every deployment failure is visible in Telegram, not just production
- Staging failures stop competing for on call attention
Built for DevOps teams · SRE teams · release engineers · platform engineers
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
app.harness.ioin a real browser with your saved login - no setup, no API keys. -
1
Harness - check deployments for a failure
- Open Harness and check the latest deployment on each pipeline
- Capture the service, environment, and failure reason for anything that failed or rolled back
- Separate out anything that happened in production
Done when Every newly failed or rolled back deployment is listed with its service and environment.
-
2
Telegram - post the failure to the team
telegram.org
WebRun opens Telegram to post the failure to the team. - Post each newly failed deployment to the team channel
- Show the service, environment, and failure reason
- Note which ones are also being escalated to on call
Done when The team channel has a post for every newly failed deployment.
-
3
Twilio - text on call for a production failure
twilio.com
WebRun opens Twilio to text on call for a production failure. - Text the on call engineer only for failures in production
- Name the service and failure reason
- Skip the text for failures in staging or lower environments
Done when The on call engineer has a text for every production deployment failure.
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 retry the deployment or roll back further?
No. WebRun only reports what happened. Retrying a deployment or taking further rollback action is always done by your engineers.
Why text only for production?
So the on call engineer's phone is reserved for what actually affects customers. Staging and lower environment failures still post to Telegram for visibility.
Does Harness's own auto rollback still work normally?
Yes. WebRun only reports on what Harness already did. It does not change your rollback configuration.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.