Share via

Power Automate throwing 502 BadGateway error.

Anonymous
2023-06-15T18:27:00+00:00

I have power automate flows running to execute Kusto queries. They were running fine until yesterday and started failing all of a sudden with a 502 bad gateway error. The queries run fine when executed directly but fail when run through flows. Can anyone help here?

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-06-16T08:56:42+00:00

    You’re very welcome, in the mean time is there anything else I can help you with today?

    Kind regards

    Tim

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2023-06-15T20:21:07+00:00

    Hi Yash26,

    I'm Tim, an Independent Consultant here and a Microsoft user like you. I don't work for Microsoft and do not have access to any of your data on their system.

    If your Power Automate flows that execute Kusto queries started failing with a 502 Bad Gateway error, there could be a few potential causes for this issue. Below are some troubleshooting steps you can try:-

    1. Check Kusto service status: Verify if there are any known service disruptions or issues with the Kusto service. Visit the Microsoft Azure Service Health dashboard or the Kusto service-specific status page to check for any reported incidents.
    2. Examine flow configuration: Review the configuration of your Power Automate flows that execute Kusto queries. Ensure that the connection settings, authentication credentials, and query parameters are correct and haven't changed unexpectedly.
    3. Test connectivity: Verify if there are any network connectivity issues between Power Automate and the Kusto service. Ensure that the environment where Power Automate is running has proper access to reach and communicate with the Kusto service. Check for any firewalls, proxy settings, or network configurations that could be blocking the flow's communication.
    4. Retry the flow: Sometimes, transient issues can cause a temporary failure. Retry running the Power Automate flows that execute Kusto queries to see if the problem persists. It's possible that the failure was due to a temporary glitch or network hiccup.
    5. Review flow limits and resource utilization: Ensure that your flow is not hitting any limitations or exceeding resource quotas. Check if you have reached any usage limits or if there are resource constraints that might be causing the 502 Bad Gateway error. Review the documentation for Power Automate and the Kusto service to understand any specific limits or recommendations.
    6. Contact Microsoft support: If the issue persists and you've exhausted the above troubleshooting steps, it's recommended to contact Microsoft support for further assistance. They can investigate the issue more deeply, analyze the flow execution logs, and provide specific guidance or solutions based on your environment and configurations.

    I hope this information helps. If you have any questions, please let me know and I'll be glad to assist you further or If you find it helpful, you can mark this comment as the answer.

    Kind regards

    Tim

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2023-06-16T05:02:56+00:00

    Thanks Tim. Will check the steps and reach out if I exhaust all the options you mentioned.

    0 comments