Automated LaunchDarkly Approval Queue Digest
Every morning, WebRun signs in to LaunchDarkly, lists the approval requests still open across your environments, captures the flag, the requester, the named reviewer, and how long each has been waiting, posts the queue to Microsoft Teams grouped by reviewer, and pings the release owner on Telegram when something is blocking a rollout.
How do I stop feature flag approvals from sitting unreviewed?
WebRun opens LaunchDarkly every morning and lists the approval requests still waiting, with the flag, the environment, the reviewer named on each, and how long it has sat. It posts the queue to Microsoft Teams grouped by reviewer and pings the release owner on Telegram, without approving anything.
- Every waiting request is named with its reviewer and its age
- A rollout stops being held up by an approval nobody noticed
- Production requests sit at the top of the queue, not buried in it
Built for release managers · platform engineers · engineering leads · DevOps teams
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.launchdarkly.comin a real browser with your saved login - no setup, no API keys. -
1
LaunchDarkly - list waiting approval requests
launchdarkly.com
WebRun opens LaunchDarkly to list waiting approval requests. - Sign in to LaunchDarkly and list the approval requests that are still pending in each environment
- Capture the feature flag, the change requested, the requester, and the reviewer named on it
- Work out how many hours or days each request has been waiting
- Note any scheduled change that depends on an approval landing first, since those turn into a missed window
- Approve nothing. WebRun reports the queue and never approves, rejects, or applies a flag change
Done when Every pending approval request is listed with its reviewer and its age.
-
2
Microsoft Teams - post the queue by reviewer
microsoft.com
WebRun opens Microsoft Teams to post the queue by reviewer. - Post the engineering channel this morning's queue grouped by the reviewer who owns it
- Give each line the flag, the environment, the change, and how long it has waited
- Put production requests and anything blocking a scheduled change at the top
- Say nothing on a morning when the queue is empty
Done when Each reviewer can see only the requests waiting on them.
-
3
Telegram - ping the release owner
telegram.org
WebRun opens Telegram to ping the release owner. - Send the release owner a short Telegram message when a request has waited past your limit
- Name the flag, the environment, the reviewer, and the release it is holding up
- Keep it to the requests that actually block something, so the ping stays worth reading
Done when The release owner knows who is blocking which change.
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 requests itself?
No. WebRun only reads the pending queue and reports it. Approving, rejecting, or applying a flag change stays with the named reviewer, because a flag change in production takes effect for real users immediately.
Does it cover every environment?
Yes. Each environment you connect is read in the same morning run, and production requests are pushed to the top of the queue so the riskiest waiting change is the first thing anyone sees.
When does the release owner get pinged?
Once a request has waited longer than the limit you set, or when it is blocking a scheduled change. Everything else stays in the Teams queue so the Telegram ping means something is genuinely stuck.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.