You’re offline. This is a read only version of the page.
Announcements
It sounds like you're dealing with a tricky issue. The 504 Gateway Timeout error typically indicates that the server didn't receive a timely response from another server. Here are some steps you can take to troubleshoot this problem:
Check Network Connectivity: Ensure that there are no network issues between your new environment and the Azure API. Sometimes, network latency or interruptions can cause timeout errors.
Review API Configuration: Verify that the API configuration in the new environment matches the older environment. Check for any differences in settings, especially related to OAuth and endpoint URLs.
Increase Timeout Settings: If possible, increase the timeout settings for the API calls in your custom connector. This can sometimes resolve timeout issues.
Check Cluster Differences: Since the new environments are on a different Microsoft cluster, there might be differences in how the clusters handle requests. You can check the cluster documentation or contact Microsoft support for more details.
Correlation ID and Gateway Name: Use the correlation ID and gateway name provided in the error message to trace the issue. Microsoft support can help you analyze these identifiers to pinpoint the problem.
Solution Checker: Run the Solution Checker in Power Platform to validate your custom connector against best practices and identify any issues.
Logs and Monitoring: Check the logs and monitoring tools for any errors or warnings that might give more insight into the issue.
If these steps don't resolve the issue, you might need to contact Microsoft support for more detailed assistance. They can help you analyze the correlation ID and gateway name to find the root cause.
If the response is helpful to you, a like or mark as the correct solution. thank you so much!
Share
Report
All responses (
Answers (
1,827
