web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Intermittent Gateway t...
Power Automate
Suggested Answer

Intermittent Gateway timeout error on friday

(1) ShareShare
ReportReport
Posted on by 2
Facing gateway timeout error when power automate is connecting to our AWS account to transfer a file, file transfer is failing with this error intermittently.
I have the same question (0)
  • Suggested answer
    Jon Unzueta Profile Picture
    1,827 Super User 2025 Season 2 on at
     
     

    A gateway timeout error when Power Automate connects to your AWS account to transfer a file typically indicates that the request is taking too long to complete, and the connection is being dropped. Since this is happening intermittently, it suggests that the issue may be related to network latency, file size, AWS service response time, or Power Automate timeout limits.

    Here’s a breakdown of what you can do to troubleshoot and resolve this:


     1. Check File Size and Transfer Time

    • Power Automate has a default HTTP timeout of 120 seconds for most connectors.
    • If the file is large or the AWS service (e.g., S3, Lambda, API Gateway) is slow to respond, the flow may time out.
    • Solution: Try compressing the file or splitting it into smaller chunks.

     2. Use Retry Policies

    • In your Power Automate flow, configure retry policies on the step that connects to AWS:
      • Click on the step → Settings → Enable retry policy
      • Choose Exponential Backoff with 3–5 retries

     3. Optimize AWS Endpoint

    • If you're using an API Gateway or Lambda, ensure:
      • The Lambda function has enough memory and timeout settings
      • The API Gateway timeout is set to the maximum (29 seconds for REST APIs)
    • For S3, ensure the bucket is in the same region as your integration to reduce latency.

     4. Use Azure Integration Runtime (if applicable)

    • If you're using Data Factory or Power Automate with Azure Data Lake, consider using an Azure Integration Runtime to improve performance and reliability.

     5. Log and Monitor

    • Add logging to your flow to capture:
      • File size
      • Transfer duration
      • AWS response codes
    • Use AWS CloudWatch or S3 access logs to correlate with Power Automate failures.

     6. Consider Using Azure Logic Apps

    • If the flow is mission-critical and needs more control over timeouts and retries, Azure Logic Apps offers more advanced configuration than Power Automate.
     
    🏷️ Tag me if you have any further questions or if the issue persists.
    ✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems.
    ❤️ Give it a Like if you found the approach useful in any way.
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 501 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 323 Moderator

#3
abm abm Profile Picture

abm abm 237 Most Valuable Professional

Last 30 days Overall leaderboard