Failed to establish a connection with the Dynamic Routing Se

Error message

Failed to establish a connection with the Dynamic Routing Server

What it means

Error "Failed to establish a connection with the Dynamic Routing Server" thrown in juspay/hyperswitch.

Source

Thrown at crates/external_services/src/grpc_client.rs:130

        let client =
            hyper_util::client::legacy::Client::builder(hyper_util::rt::TokioExecutor::new())
                .http2_only(true)
                .build_http();
        // deja: wrap the shared pool in the gRPC egress boundary at its one
        // construction site.
        #[cfg(all(
            any(feature = "dynamic_routing", feature = "revenue_recovery"),
            feature = "deja"
        ))]
        let client = deja_transport::DejaGrpcTransport::new(client);

        #[cfg(feature = "dynamic_routing")]
        let dynamic_routing_connection = self
            .dynamic_routing_client
            .clone()
            .map(|config| config.get_dynamic_routing_connection(client.clone()))
            .transpose()
            .expect("Failed to establish a connection with the Dynamic Routing Server")
            .flatten();

        #[cfg(feature = "dynamic_routing")]
        let health_client = HealthCheckClient::build_connections(self, client.clone())
            .await
            .expect("Failed to build gRPC connections");

        let unified_connector_service_client =
            UnifiedConnectorServiceClient::build_connections(self).await;

        #[cfg(feature = "revenue_recovery")]
        let recovery_decider_client = {
            match &self.recovery_decider_client {
                Some(config) => {
                    // Validate the config first
                    config
                        .validate()
                        .expect("Recovery Decider configuration validation failed");

View on GitHub (pinned to 705a321950)

Solutions

Verify the Dynamic Routing Server address in config and that the service is running and reachable
Check TLS/cert settings for the gRPC connection

When it happens

Trigger: Thrown at crates/external_services/src/grpc_client.rs:130 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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