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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / 'Run_a_flow_built_with...
Power Automate
Suggested Answer

'Run_a_flow_built_with_Power_Automate_for_desktop' TimedOut While waiting for operation to complete

(2) ShareShare
ReportReport
Posted on by 4
Error details:
ActionTimedOut. The workflow action 'Run_a_flow_built_with_Power_Automate_for_desktop' timed out while waiting for underlying operation to complete.

May times our cloud flow fails due to TimedOut and we couldn't get the details at what step/action flow is failed. 
Is there any way to get the specific action details which caused the timedout?
 

 
ActionTimedOut.png
I have the same question (0)
  • Suggested answer
    trice602 Profile Picture
    16,239 Super User 2026 Season 1 on at
     
    Yes you can see the actual steps that occurred and where it failed by following these steps:
     
     
    1) click on desktop flow activity
    2) scroll down to recent desktop flow runs
    3) select the recent run you want to see and you will be able to see all the PAD steps and all the details.
     
     
    This is going to show you every step/action that occurred, what the input and output was and also show you the step where the error occurred.  Something PAD will also take a screenshot of the step that failed to help you see it too.
     

    ------------------------------------------------

     

     

    ⭐ If this was helpful, please like and check the box below "Does this answer your question" to help others find this too!

     

     

    Always glad to help! 💯💯💯💯💯

     

    Tom

     

    Follow me on LinkedIn - Thomas Rice, PMP | LinkedIn

  • Suggested answer
    Riyaz_riz11 Profile Picture
    4,150 Super User 2026 Season 1 on at
    HI,
     

    Solution 1: Enable Detailed Logging in PAD Flow

    Add logging throughout your PAD flow:

    1. Add "Set variable" actions at key points in your PAD flow:
      Set variable: LogStep to "Step 1: Starting process"
      Set variable: LogStep to "Step 2: Opening Excel"
      Set variable: LogStep to "Step 3: Processing data"

    2. Return the log variable as output:

      • In PAD flow outputs, include LogStep

      • This will show you the last completed step before timeout

    Solution 2: Use Exception Handling with Logging

    Wrap critical sections in try-catch blocks:

    Try
        // Your Excel operations here
        Set variable: LogStep to "Excel operations completed"
    Catch
        Set variable: LogStep to "Excel operations failed: " + Exception.Message
        Set variable: ErrorOccurred to True
    End Try

    Solution 3: Break Down Large Operations

    Split your PAD flow into smaller, manageable chunks:


    1. Create multiple smaller PAD flows instead of one large flow

    2. Call them sequentially from your cloud flow

    3. Each call will have its own timeout, making it easier to identify the problematic section

    4.  

    Example structure:


    • PAD Flow 1: Data preparation (2-3 minutes)

    • PAD Flow 2: Excel processing (2-3 minutes)

    • PAD Flow 3: Final output (1-2 minutes)

    Solution 4: Implement Progress Tracking

    Use a SharePoint list or file to track progress:

    1. Create a status tracking method in your PAD flow:
      Write text to file: "Step 1 completed at " + CurrentDateTime
      Write text to file: "Step 2 completed at " + CurrentDateTime

    2. Check this log file when timeout occurs to see exactly where it stopped

    Solution 5: Optimize PAD Flow Performance

    Identify and fix performance bottlenecks:


    1. Add timing measurements:
      Set variable: StartTime to CurrentDateTime
      // Your operations
      Set variable: Duration to CurrentDateTime - StartTime

    2. Common performance issues to check:

      • Large Excel files (consider processing in chunks)

      • UI automation waits (reduce or optimize)

      • File I/O operations (batch them)

      • Network calls (add proper timeouts) 

      •  

    Solution 6: Use Cloud Flow Timeout Settings

    Adjust timeout settings in your cloud flow:


    1. In the PAD action settings, increase timeout:

      • Go to Settings → Timeout

      • Increase from default (usually 30 minutes) to 60+ minutes

      •  

    2. Add intermediate checkpoints in cloud flow to monitor progress
     

    Solution 7: Implement Heartbeat Mechanism

    Create a heartbeat system:


    1. In PAD flow, periodically update a status file:
      Every 30 seconds: Write "Alive: " + CurrentDateTime to status file
    2. In cloud flow, check this file to monitor if PAD is still running

    3.  

    Solution 8: Use Run History Analysis

    Enable detailed run history:


    1. In PAD, go to Settings → Logging

    2. Enable verbose logging

    3. Check run history in PAD console for specific failure points

    4.  

    Solution 9: Staged Execution with Checkpoints

    Implement checkpoint-based execution:

    // At each major step
    If CheckpointFile exists Then
        Read last checkpoint
        Skip to appropriate step
    Else
        Start from beginning
    End If
    
    // Save checkpoint after each major operation
    Write "Checkpoint: Step X completed" to file

    Solution 10: Alternative Architecture

    Consider hybrid approach:


    1. Use cloud flow for coordination

    2. Use PAD for specific desktop tasks only

    3. Use Office 365 connectors for Excel operations where possible

    4. Store intermediate results in SharePoint/OneDrive


    5.  
     

    Best Practice Implementation

    Here's a recommended approach:


    1. Break your PAD flow into 3-5 smaller flows

    2. Add logging at the start/end of each major operation

    3. Use try-catch blocks around critical sections

    4. Implement progress tracking via file or SharePoint list

    5. Set realistic timeouts based on actual operation times

    6. Monitor and optimize the slowest operations

    7.  

    Example logging structure:

    Try
        Set variable: LogMessage to "Starting Excel processing"
        Write LogMessage to file
        // Excel operations
        Set variable: LogMessage to "Excel processing completed"
        Write LogMessage to file
    Catch
        Set variable: LogMessage to "Excel processing failed: " + Exception.Message
        Write LogMessage to file
    End Try
     
     
    If I have answered your question, please mark it as the preferred solution ✅ . If you like my response, please give it a Thumbs Up 👍.
    Regards,
    Riyaz

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Vish WR Profile Picture

Vish WR 816

#2
Valantis Profile Picture

Valantis 603

#3
Haque Profile Picture

Haque 566

Last 30 days Overall leaderboard