Overview
An issue was identified where the “Send to Closer” action failed due to webhook execution errors, with insufficient error details available for troubleshooting.
This update focuses on resolving the lack of visibility into webhook failures and improving system diagnostics.
Resolution Summary
The system has been updated to enhance how webhook failures are handled, recorded, and displayed.
Implemented Improvements
1. Failure Execution Logging Enabled
Webhook executions that result in failure are now consistently recorded in Webhook Logs
Each log entry includes:
Trigger name
Execution timestamp
Status code
Associated profile/action
This ensures all execution attempts are traceable.
2. Detailed Error Capture (HTTP Response)
The system now captures the actual response returned by the endpoint
Example (from current behavior):
Status Code: 404 (Not Found)
Response Body: HTML error page returned by the destination server
This confirms that:
The request reached the endpoint
The endpoint responded with an error (not a system failure)
3. Improved Error Visibility in UI
The Process Result section now displays:
Raw response returned by the webhook endpoint
HTML or JSON error content (when applicable)
This allows users to:
Identify incorrect URLs (e.g., 404 errors)
Detect misconfigured endpoints
Validate endpoint availability directly from logs
Resulting Behavior
After the update:
Webhook failures:
Are fully logged under Webhook Logs
Include HTTP status codes and response payloads
Example interpretation:
404 Error → Endpoint URL is incorrect or not found
5xx Errors → External service issue
Timeout/No response → Connectivity issue
The issue has been resolved by implementing comprehensive logging and detailed error reporting for webhook executions. This ensures that all failures are transparent, traceable, and actionable moving forward.