Skip to content

Conversation

@rjnz2023
Copy link

@rjnz2023 rjnz2023 commented Dec 9, 2025

Summary

When dealing with high event volumes, webhooks can end up with very large payloads that may overwhelm the receiving endpoint. This PR adds a configurable batch-size option that limits how many events are included in each webhook request.

Key changes:

  • New batch-size config option under webhook.<id>.batch-size (defaults to 100)
  • Events beyond the batch limit are queued for the next delivery cycle
  • Invalid batch sizes trigger a warning and fall back to the default

Configuration

[webhook.my-webhook]
url = "https://example.com/webhook"
batch-size = 50  # Send max 50 events per request

Testing

  • Verified compilation with cargo check
  • Logic ensures remaining events are scheduled for delivery after throttle interval

There's a companion PR for the webadmin UI to expose this setting.

mdecimus and others added 3 commits November 19, 2025 15:35
When dealing with high event volumes, sending all events in a single
webhook request can result in oversized payloads. This adds a
configurable batch-size option (default: 100) that limits how many
events are included per request.

Remaining events are automatically queued for the next delivery cycle
based on the throttle setting.
@CLAassistant
Copy link

CLAassistant commented Dec 9, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ rjnz2023
❌ mdecimus
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants