Power Automate - Building Flows

When a new email arrives v3 bad gateway

Like (2) Share

Report

Posted on 7 Oct 2024 18:01:23 by Shegs

since yesterday this trigger has stopped working for me. no reason why.

the error is timeout.

Categories:

Business Process Flows

All responses (3)

Answers (0)

Robu1 1,218 Super User 2025 Season 1 on 07 Oct 2024 at 21:01:47

Like (0)

Report

When a new email arrives v3 bad gateway

Hi @shegs,

Seems like a temporary issue.

I would see if it works at a later time.

Cheers,

Rebecca
Shegs 87 on 07 Oct 2024 at 20:37:46

Like (0)

Report

When a new email arrives v3 bad gateway

unfortunately, none of those suggestions help in this situation.

can't retry the flow because the trigger is what is failing.

the connectivity is fine, I am connected to the inbox in outlook with no issues

error handling helps after the flow is triggered

resource limits wouldn't trigger. these have been running fine for months if not a year now.
Suggested answer

Robu1 1,218 Super User 2025 Season 1 on 07 Oct 2024 at 19:54:07

Like (0)

Report

When a new email arrives v3 bad gateway

Hi Shegs ,

Thank you for choosing Microsoft Community.

Got it! A “502 Bad Gateway” error in Power Automate usually indicates that the server acting as a gateway or proxy received an invalid response from an upstream server.

Here are some steps you can take to troubleshoot this issue:

Check Service Status: Verify if there are any known service disruptions with Power Automate or the connected services.

You can check the Microsoft Service Health dashboard for any ongoing issues. None at the moment.

https://admin.cloud.microsoft/?#/servicehealth/:/alerts/MO889023.

Review Flow Configuration: Ensure that your flow’s configuration, including connection settings and authentication credentials, is correct. Sometimes, changes in these settings can cause errors.

Test Connectivity: Make sure there are no network connectivity issues between Power Automate and the service you’re trying to connect to. Check for any firewalls, proxy settings, or network configurations that might be blocking the connection.

Retry the Flow: Sometimes, transient issues can cause temporary failures. Try running the flow again to see if the problem persists.

Check for Resource Limits: Ensure that your flow is not hitting any usage limits or resource constraints. Review the documentation for any specific limits or recommendations.

Error Handling: Implement error handling in your flow to manage and log errors effectively. You can use the “Configure run after” option to handle errors and take appropriate actions.

If this fixes the issue, please mark as resolved to help others with find it.

Happy to help.

Robu 1

Community site session details

When a new email arrives v3 bad gateway

Helpful resources

News and Announcements

Quick Links

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Warren Belz – Community Spotlight

Congratulations to the April Top 10 Community Stars!

Leaderboard > Power Automate - Building Flows

Featured topics

Product updates

Community site session details

When a new email arrives v3 bad gateway

Helpful resources

News and Announcements

Quick Links

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Warren Belz – Community Spotlight

Congratulations to the April Top 10 Community Stars!

Subscribe to this forum!

Select categories

Leaderboard > Power Automate - Building Flows

Featured topics

Product updates