Cause of intermittent 'BadRequest' error in Send Multiple Events action for Azure Event Hubs

Question

I use the Send Multiple Events built-in connector action in a Azure Logic Apps Standard stateful workflow and I've recently started getting random 'BadRequest' errors. The action is not automatically retried in such a situation, but having implemented an explicit routine to attempt delivery several times, the request will ultimately go through to the Event Hub.

This is the more detailed error I get:

{
    "statusCode": "BadRequest",
    "body": {
        "code": "ServiceProviderActionFailed",
        "message": "The service provider action failed with error code 'BadRequest' and error message 'No such host is known.'."
    }
}

What could be root cause for such an error?

Answer 1

Hi @Veli-Jussi Raitila ,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

The root cause of the error "No such host is known" in your Azure Logic Apps workflow is likely a DNS resolution failure when trying to connect to your Event Hub. This typically means that at the time of the request, the DNS server could not resolve the Event Hub’s hostname (.servicebus.windows.net) to an IP address. Possible reasons include intermittent issues with DNS servers, such as temporary unavailability or misconfiguration. It could also be caused by network connectivity issues between Logic Apps and the Event Hub, or even misconfigured endpoints in the Event Hub itself. Additionally, transient platform issues on Azure, such as service disruptions or high load, can cause DNS resolution or network connectivity failures. These issues can sometimes be intermittent and resolved upon retries, which is why your explicit retry logic may eventually succeed.

Please do let me know if you have any further queries. I would be happy to assist you.

Thank you.