A burst of deliveries to one webhook drains at about one per timeout
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp
- Domain
- backend, distributed-systems, performance
Research direction
Read src/plugins/FluentCMS.Plugins.Webhooks/WebhookDeliveryJob.cs:142-151 and WebhookQueueTests.TwoDeliveriesToOneWebhookNeverRunAtOnce first. Trace how a completed delivery schedules the next waiting attempt and how attempts are ordered by event time. Done means bursts reach a fast receiver at roughly its response time per event, in event order, without waiting jobs rerunning while another attempt is in flight.
Written by the indexing model from the issue text.
Description
Problem
While a webhook has an attempt in flight, WebhookDeliveryJob (src/plugins/FluentCMS.Plugins.Webhooks/WebhookDeliveryJob.cs:142-151) reschedules every other attempt for it to busy.CreatedAt + Timeout plus jitter, the worst-case end of the send. WebhookQueueTests.TwoDeliveriesToOneWebhookNeverRunAtOnce asserts that wait. 1,000 events to a receiver that answers in 200 ms take hours; each round re-runs every waiting job (O(N²)) on the webhooks queue all sites share; jitter reorders events of one entry.
Proposal
Let a finished attempt wake the oldest waiting one (or keep a per-webhook FIFO drained by one job), order attempts by event time, and back off from now rather than from the worst case if polling stays.
Acceptance
- N events to a fast receiver are delivered in about N times its response time, in event order
- Waiting attempts do not re-run while one is in flight
Found in the code review of 17 Nov 2026 (P1).
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a 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 fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:build security type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:sdk security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
microsoft/microsoft-ui-reactor#1567 ·
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100