Set variable actions that you had to remember to delete before pushing to production.Microsoft has addressed this bottleneck in Power Automate for desktop by allowing makers to assign default debugging values directly to flow variables inside the desktop flow designer. Tracked under Microsoft 365 Roadmap ID 576784 (and earlier Message Center post MC1310384), the feature reached general availability on June 23, 2026, according to Microsoft's Power Platform 2026 release wave 1 documentation. It is enabled automatically for admins, makers, marketers, and analysts in Worldwide standard multi-tenant environments without requiring an administrative toggle.
What Changed in the Desktop Flow Debugger
Before this capability arrived, Power Automate for desktop already offered a standard Run from here action on the right-click context menu. While convenient, jumping straight to a middle step skipped all the upstream actions that normally populated your flow variables, leaving downstream logic to fail on empty or uninitialized states unless you paused execution at a breakpoint and edited live values by hand.
With default-value debugging, Microsoft separates a variable's Variable value (its live runtime state) from its Default value (a preset state reserved for mid-flow debugging). When you initiate a debug run from a specific step using the dedicated default-value command, the designer automatically injects those preconfigured defaults rather than recomputing the variables from step one.
According to Microsoft's release plan documentation, these default values are strictly scoped to debugging sessions and do not affect production executions. When you are done troubleshooting a branch, clearing the default value restores standard variable handling.
Step-by-Step: How to Debug a Flow Using Default Variable Values
Microsoft Learn's variable management documentation outlines the exact procedure for configuring and triggering a default-value debug run in the Power Automate desktop flow designer:
- Locate the target variable: In the desktop flow designer, open the Variables pane on the right side of the workspace, which lists your input/output variables and Flow variables. (Note: Power Automate automatically hides variables belonging to disabled actions; you must enable a disabled action for its variables to appear in the pane.)
- Open the variable editor: Double-click the desired flow variable—or open its context menu—to launch the Edit flow variable dialog.
- Define the default state: Set the Default data type and enter the desired Default value. If you are working with complex structures containing nested elements, such as custom objects inside custom objects, you can select More to inspect nested properties and use the top arrow icon to navigate back to the parent element.
- Save the configuration: Click Save to store the debugging default.
- Launch execution from your target step: In the main workspace canvas, right-click the specific action where you want your test scenario to begin and select Run from here with default values, or press the keyboard shortcut Alt+F5.
- Clean up when finished: To disable the behavior after validating your conditional logic, reopen the Edit flow variable dialog and clear the Default value field.
Comparing Debugging Approaches in Power Automate for Desktop
Based on Microsoft Learn's debugging and variable documentation, makers now have three distinct ways to manipulate state during desktop flow testing, each suited to a different troubleshooting scenario:
| Debugging Method | How It Is Triggered | Variable Behavior | Best Used When... |
|---|---|---|---|
| Run from here | Right-click an action and select Run from here | Ignores previous actions; does not seed flow variable defaults | Downstream steps do not depend on variables populated earlier in the flow. |
| Run from here with default values | Right-click an action and select Run from here with default values (Alt+F5) | Automatically applies configured Default value settings to flow variables | Testing complex conditions, loops, or branches deep in a flow without re-running upstream UI or API steps. |
| Live Variable Editing | Pause at a breakpoint, double-click a variable, edit Variable value, and click Save | Overrides the live in-memory value during an active, paused debug run | Inspecting state mid-flight and nudging a single number, boolean, text, or datetime value on the fly. |
Notice that within the Edit flow variable dialog during a paused run, you can also click the revert icon next to the live Variable value field to reset it to your configured Default value immediately.
Practical Caveats, Security Warnings, and Limitations
While seeding default states is a major time-saver for RPA developers, Microsoft Learn's documentation highlights several architectural boundaries and security considerations you should keep in mind before populating defaults across your flows:
- Upstream external state is still skipped: Starting a flow at step 30 with
Alt+F5populates your configured variable defaults, but it still bypasses steps 1 through 29. If action 30 expects an application window to be open or a web session to be authenticated on the local Windows machine, that external state must already exist on your desktop. - Instance and session inputs do not support defaults: Do not confuse Flow variables with Input variables (which pass data from cloud flows or the console into desktop flows). While standard input variables (such as text, number, boolean, list, custom object, or datatable) support default values for designer or console runs, Microsoft Learn explicitly notes that instance- and session-type input variables—specifically Browser (Edge, Chrome, or Firefox), Excel, Word, Outlook, Access, and Terminal—do not support default values. To test flows using those inputs in the designer, you must temporarily initialize them as produced variables from corresponding
Launch,Open, orAttachactions. - Never store real secrets in default values: Power Automate allows makers to mark variables as sensitive, which masks their values in the designer UI and omits them from portal run history logs when using an organization premium account. However, Microsoft warns that marking a variable as sensitive does not protect hardcoded plain-text data or default values. For sensitive input variables, default values remain visible in the creation and editing dialogs and are stored unprotected in action modals and the underlying flow definition in Microsoft Dataverse. Always use dummy or synthetic test data for debugging defaults rather than real passwords, API keys, or PINs.
- Version compatibility lock-in: As a general platform rule documented by Microsoft, any desktop flow built or edited with Power Automate for desktop version 2.14 or later cannot be opened or executed by older client versions, with no workaround other than keeping your desktop clients updated.
For enterprise developers and Windows automation specialists, Run from here with default values removes one of the most tedious parts of RPA maintenance. By pairing Alt+F5 with representative test payloads in the Variables pane, you can isolate and verify deeply nested conditional branches in seconds—without risking leftover test scaffolding in your production automation.