Stop releases sitting idle on a pending approval
Every hour, WebRun opens Harness, looks through the running pipeline executions for any paused on an approval step, records which pipeline, service, and environment is waiting and for how long, drafts a reminder email to the named approver in Gmail and leaves it unsent, and pings your release manager on WhatsApp with anything parked for too long.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I stop deployments waiting on a manual approval?
WebRun checks Harness every hour for pipeline executions paused on an approval step, recording the service, environment, approver, and wait time. It drafts an unsent reminder to each approver in Gmail and pings your release manager on WhatsApp, so a release never sits parked overnight unnoticed.
- A parked release is chased within the hour, not the next morning
- Every approver gets one drafted reminder covering all their pending steps
- Nothing is approved or deployed without a human clicking it
Built for release managers · DevOps engineers · platform teams · engineering leads
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 - find executions waiting on approval
WebRun opens Harness to find executions waiting on approval. - Open Harness and list the pipeline executions currently running
- Find the ones paused on an approval step rather than executing or failed
- Record the pipeline, the service, the target environment, and how long it has waited
- Note who the approval is assigned to and who triggered the execution
Done when Every execution waiting on an approval is listed with its owner and wait time.
-
2
Gmail - draft the reminder to the approver
WebRun opens Gmail to draft the reminder to the approver. - Draft one email per approver listing the pipelines waiting on them
- Include the service, the environment, the wait time, and a link to the execution
- Leave every email as an unsent draft. WebRun never emails an approver on its own, so you decide when a nudge goes out
Done when An unsent reminder draft exists in Gmail for each approver with work waiting.
-
3
WhatsApp - ping the release manager
WebRun opens WhatsApp to ping the release manager. - Message the release channel with the pipelines still parked on an approval
- Put the longest wait first with the environment named, so a production release is not buried
- Say plainly which drafts are waiting in Gmail for a human to send
Done when The release manager knows what is parked and for how long.
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 approve the pipeline itself?
No. WebRun never clicks an approval, never promotes a release, and never rolls one back. It reports what is waiting and drafts the reminder, and a named human still makes the call.
Will it email approvers without me?
No. Each reminder is left as an unsent Gmail draft. You review and send it, so an approver is never chased by an automated email you did not see.
How long before something is called parked?
You set the threshold, commonly an hour for production and longer for lower environments. Anything over it leads the WhatsApp message with its wait time shown.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.