New Feature: Configurable Webhook Timeouts

We've added the ability to configure custom HTTP connection timeouts for individual webhooks, giving you greater control over integration behaviour when connecting to external systems with varying response times.

What's New

Previously, all webhooks used the default system timeout configuration. Some integrations with slower external systems would fail prematurely, while others didn't need to wait as long. You can now set custom timeout values on a per-webhook basis to match the specific needs of each integration endpoint.

What's Included

Custom Timeout Configuration: Set timeout values between 1 and 300 seconds (5 minutes maximum) for any webhook
Flexible Configuration: Leave the timeout empty to use default system settings, or specify a custom value for integrations that need it
UI Guidance: Helpful tooltips explain the valid range and default behavior directly in the webhook configuration form

How It Works

When creating or editing a webhook in Settings → Integrations → Outbound Integration → Webhooks:

• Navigate to the webhook configuration form
• Locate the new "Timeout (seconds)" field
• Enter a value between 1-300 seconds, or leave empty for default behaviour
• Save the webhook configuration

Benefits

Reduced Failed Integrations: Longer timeouts prevent premature failures when connecting to slower external systems or APIs with longer processing times.
Improved Performance: Shorter timeouts allow faster failure detection for webhooks that should respond quickly, reducing unnecessary waiting.
Better Control: Fine-tune each webhook's behaviour independently based on the specific requirements of the external system.
Fully Backward Compatible: Existing webhooks continue using default timeout settings—no changes required to current configurations.

Use Cases

• Set longer timeouts (120-300 seconds) for webhooks that trigger complex processing or batch operations
• Use shorter timeouts (5-15 seconds) for simple notifications that should respond quickly
• Match timeout values to external system SLAs and documented response time expectations

Bug Fixes

Email Auto-Forward to Multiple Recipients

Issue Resolved: Fixed issues with the email Auto Forward functionality to improve delivery reliability and content handling. The system now properly manages forwarded email instances throughout the delivery process.