Skip to main content

Timeout for Power Automate Desktop Flows

In Power Automate Desktop (PAD) there’s no built-in “auto-kill after X minutes” setting, so you have to enforce the 10-minute limit yourself. Here are the three reliable ways, from best practice to more advanced.


Best practice: Control it from a Cloud Flow (recommended)

This is the cleanest and safest approach.

How it works

  • A Cloud flow starts the Desktop flow

  • You set a timeout of 10 minutes

  • If the desktop flow runs longer → it gets terminated automatically

Steps

  1. Create a Cloud flow

  2. Add action: Run a flow built with Power Automate for desktop

  3. Click … (three dots) on the action → Settings

  4. Set Timeout to:

    PT10M

  5. Enable Run in unattended mode if needed

  6. Save

If the desktop flow exceeds 10 minutes, Power Automate will force stop it

Pros

  • Official, supported

  • No hacks

  • Best for production



Option 2: Build a timeout watchdog inside the Desktop Flow

Use this if you must run PAD standalone.

Basic logic

  1. At the start of the flow, store the current time

  2. During loops or long actions:

    • Check elapsed time

    • If > 10 minutes → Terminate flow

Example logic

  • Action: Get current date and time → StartTime

  • Inside loops:

    • Get current date and time → Now

    • Subtract datetimes

    • If ElapsedMinutes > 10:

      • Use Terminate flow action

Pros

  • Works offline

  • No cloud flow needed

Cons

  • Only stops at checkpoints (not mid-action)


Option 3: Force-kill the process (advanced / last resort)

You can externally kill PAD if it hangs.

Method

  • Use another flow / scheduled task to run:

    taskkill /IM PAD.Console.Host.exe /F

    or

    taskkill /IM PAD.DesktopPlayer.exe /F

Cons

  • Abrupt stop

  • Can corrupt sessions

  • Not recommended unless recovery automation is required

Comments

Post a Comment

Popular posts from this blog

Key Limitations of Microsoft Power Automate (as of August 2025)

Microsoft Power Automate is a powerful tool for automating business processes, but like any platform, it comes with a set of limitations. Understanding these constraints is essential to designing efficient, scalable, and compliant workflows—especially as your automation strategy grows in complexity.  Here are the most important limits you need to know:  1. Switch Cases Each Switch action supports a maximum of 25 cases. If you need more, consider using nested Switches or alternate logic like parallel branches or conditionals.  2. Actions per Workflow A single flow can contain up to 500 actions. For complex workflows, you may need to split logic into separate flows or use child flows to stay within this limit.  3. Nesting Depth You can nest actions (e.g., conditionals or loops) up to 8 levels deep. Going beyond this will result in a design error.  4. Variables per Flow Each flow can define up to 250 variables. This includes all variable types (string, inte...
Post a Comment
Read more

Bulk Import Excel Data to SharePoint List Using PowerShell and PnP

  Managing large datasets in SharePoint can be tricky, especially when you're dealing with Excel files and need to avoid list view threshold issues. In this guide, I’ll walk you through a PowerShell script that efficiently imports data from Excel into a SharePoint Online list using PnP PowerShell — with batching support for performance. Prerequisites Make sure you have the following before running the script: SharePoint Online site URL Excel file with data properly formatted PnP PowerShell module installed ( Install-Module PnP.PowerShell ) Appropriate SharePoint permissions What the Script Does Connects to your SharePoint site Loads and reads an Excel file Converts Excel date values Batches records in groups (to avoid the 5000 item threshold) Adds the items to your SharePoint list or library Logs execution time PowerShell Script $siteUrl = "[Site Collection URL]" Connect-PnPOnline -Url $siteUrl -UseWebLogin # Capture the start time $startTime...
Post a Comment
Read more

🚀 Essential SPFx (SharePoint Framework) Commands for Every Developer

Whether you're new to SharePoint Framework (SPFx) or a seasoned pro, having a go-to list of core commands can significantly improve your development workflow. In this post, we'll walk through the most important SPFx CLI commands—from setting up your environment to packaging and deploying your solution. 🛠️ Setting Up Your SPFx Project Start by scaffolding a new project using the Yeoman generator provided by Microsoft. Make sure Node.js and npm are installed before you proceed. yo @microsoft/sharepoint After scaffolding the project, install all dependencies: npm install To update dependencies later: npm update 🔐 Trusting the Development Certificate If you're using the local workbench, you need to trust the developer certificate for HTTPS support: gulp trust-dev-cert 🧪 Running the Local Workbench To build and serve your project locally, use: gulp serve This command starts a local server at: https://localhost:4321/temp/workbench.html You can also test your solution in ShareP...
Post a Comment
Read more