juspay/hyperswitch · error · WebhookRegistrationError

CONNECTOR_EXECUTION_ERROR

CONNECTOR_EXECUTION_ERROR

Error message

err.to_string()

What it means

Error "err.to_string()" thrown in juspay/hyperswitch.

Source

Thrown at crates/router/src/core/merchant_connector_webhook_management.rs:351

            .await
            {
                Ok(resp) => resp,
                Err(err) => {
                    router_env::logger::error!(
                        error=?err,
                        connector=%connector_data.connector_name,
                        scope=?identifier,
                        "Connector webhook registration call failed; continuing with next item"
                    );
                    return Ok((
                        identifier.clone(),
                        WebhookRegistrationResult {
                            identifier: identifier.clone(),
                            status: common_enums::WebhookRegistrationStatus::Failure,
                            connector_webhook_id: None,
                            error: Some(
                                api_models::merchant_connector_webhook_management::WebhookRegistrationError {
                                    code: "CONNECTOR_EXECUTION_ERROR".to_string(),
                                    message: err.to_string(),
                                },
                            ),
                        },
                        None,
                        None,
                    ));
                }
            };

            let (result, metadata) = match response.response {
                Ok(success) => {
                    let result = WebhookRegistrationResult {
                        identifier: identifier.clone(),
                        status: success.status,
                        connector_webhook_id: success.connector_webhook_id,
                        error: None,
                    };

View on GitHub (pinned to 806ec7dcc0)

Solutions

1. Inspect the wrapped connector error (err) in logs for the real failure reason during webhook management
2. Verify the merchant connector account credentials and webhook configuration

When it happens

Trigger: Thrown at crates/router/src/core/merchant_connector_webhook_management.rs:351 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of juspay/hyperswitch@806ec7dcc0 (2026-08-19). Data as JSON: /api/errors/f668bc57fe92ea69. Report an issue: GitHub.