Debounce dashboard refresh dispatches in the webhook function
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #176 by @trask — closed without merging
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Locate the Netlify webhook function, its Netlify Blobs usage, and the existing hourly cron or scheduled function. Trace how accepted events currently dispatch workflows, then compare the implementation with the proposed repository-and-PR debounce state. Done means bursty events produce one trailing dispatch after the quiet period, updates are not dropped during concurrent writes, and the hourly backstop remains effective.
Written by the indexing model from the issue text.
Description
The Netlify webhook dispatches one workflow run per accepted event. Bursty repositories generate far more runs than the dashboard needs, and job-level concurrency then cancels most of them.
Measured on 2026-07-28 against opentelemetry-collector-contrib:
- GitHub Actions opens a separate check suite per workflow, so one push to a PR produces ~17
check_suite.completedevents, hence 17 dispatches. - Worst burst observed: 53 dispatches for a single PR in 77 seconds.
- Across a sample of 1,501 dashboard-eligible events, 82% were
check_suite.completed. - 81% of completed dashboard runs in the sampled window were cancelled by concurrency.
Every dispatch in a burst produces the same dashboard output, because each run re-reads the full statusCheckRollup. Only the last one carries new information.
Proposal: collapse events per repository + PR number before dispatching.
- On each accepted webhook, record
lastEventAtin a Netlify Blobs entry keyed by${repository}#${pr_number}instead of dispatching. - A scheduled function runs every minute and dispatches once a PR has been quiet for ~45s, then records
lastDispatchAt. - Flush on
lastDispatchAt < lastEventAtrather than a boolean, so a lost update from concurrent writes costs one extra tick instead of a dropped refresh.
Simulated against the real event stream, a 60s trailing debounce on all events removes 66% of dispatches. Leading-edge and check-suite-only variants both scored worse (54% and 52%), so the simplest policy is also the best one.
Trade-off: refresh latency goes from near zero to roughly 45-105 seconds. The hourly cron remains the backstop, and duplicate dispatches stay harmless because the existing concurrency group absorbs them.
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 23
- Avg merge
- 15h 46m
- Merged PRs (30d)
- 41
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from open-telemetry/shared-workflows
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
open-telemetry/shared-workflows#532 · 1 comment ·
Maintainers usually reply within 1 day
-
Hash-lock pull request dashboard Python dependencies (move to uv)Possibly taken @irfadkp claimed this 3 days ago. Opendashboard dependencies
Difficulty 4/5 3-5 days Newbie friendliness 51/100
open-telemetry/shared-workflows#517 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
open-telemetry/shared-workflows#492 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
open-telemetry/shared-workflows#422 ·
Maintainers usually reply within 1 day
-
Support Zizmor SARIF uploads from private repositoriesMay be free again @trask claimed this 61 days ago, and no pull request is open. Open
open-telemetry/shared-workflows#390 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in open-telemetry/shared-workflows
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
manuXD270516/descanso#80 ·
Maintainers usually reply within 2 days
-
feat: Warn while typing a forbidden character in a file namePossibly taken @Mittalnew claimed this today. Openapp Drive 📁 enhancement OO Docs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linagora/twake-drive#4620 · 1 comment ·
Maintainers usually reply within 1 day
-
国战吕蒙【谋断】问题Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Edit: Hello TasteOpenchannels:edit check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day