Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Tagged Issue
juspay/hyperswitch-cloud/issues/11764

Description

This pull request introduces validation logic for routing configuration objects and improves error handling for dynamic routing setup. The main changes ensure that required fields are present in routing configs and provide clearer error messages when configurations are missing or invalid.

Routing Configuration Validation

• Added a validate method to EliminationRoutingConfig and SuccessBasedRoutingConfig to check that at least one required field is present; returns a validation error if all fields are null. [1] [2]

Error Handling Improvements

• Updated create_specific_dynamic_routing_setup to call the new validate methods and return a specific error if the configuration is invalid, with a clear message about missing fields. [1] [2]
• Improved error mapping in link_routing_config to distinguish between not-found and internal server errors, providing more descriptive error contexts.

Code Maintenance

• Added fp_utils to imports in crates/api_models/src/routing.rs to support the new validation logic.

Routing Algorithm Logic

• Updated logic in DynamicRoutingAlgorithmRef to return false if algorithm_id is missing, ensuring more robust feature checks.

How did you test it?

create success_based with empty payload

curl --location 'http://localhost:8080/account/merchant_1762366132/business_profile/pro_OvIAO1lNAyVksNftih0N/dynamic_routing/success_based/create?enable=dynamic_connector_selection' \
--header 'Content-Type: application/json' \
--header 'api-key:****' \
--data '{}'

{
    "error": {
        "type": "invalid_request",
        "message": "All fields in SuccessBasedRoutingConfig cannot be null",
        "code": "IR_06"
    }
}

activate routing algo without descision_engine_config

curl --location 'http://localhost:8080/routing/routing_DkSrtH3FRM8olK7Mmf5s/activate' \
--header 'Content-Type: application/json' \
--header 'api-key:**** \
--data '{}'

{
    "error": {
        "type": "invalid_request",
        "message": "Config key does not exist in our records.",
        "code": "HE_02"
    }
}

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible