Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | Apr 2026 | - |
Business value
Unattended desktop flow runs often fail without clear visual context, forcing makers and support teams to reproduce issues manually or rely on incomplete logs. Existing tools, such as action logs, screenshots, and run‑history metadata, provide useful data but are sometimes insufficient, especially when failures stem from transient UI issues, timing conflicts, pop‑ups, or unexpected system behavior. Logging unattended failures can be significantly harder when only textual logs and screenshots are available.
The Video logs for unattended runs feature directly addresses this gap. When enabled, Power Automate automatically records and stores locally the last 60 seconds preceding a failure during an unattended run. Alongside the video, optional closed captions display which actions were being executed at each moment (based on the exact logging metadata captured during runtime). The result is a powerful, intuitive debugging tool that reduces the time required to identify root causes and accelerates recovery.
Feature details
This feature adds a new troubleshooting layer in the Power Automate unattended execution pipeline.
How it works When an unattended run fails and video logging is enabled, Power Automate for desktop:
- Automatically records the last 60 seconds of the machine’s screen.
- Saves the recording locally on the machine (default path:
%localappdata%\Microsoft\Power Automate Desktop\VideoLogs) - Embeds closed captions (CC) based on the executed actions so users can see exactly which step was being performed at the moment of failure.
- Makes the video available for local playback so makers can visually review what led to the error.
Closed captions (CC) with action mapping
- Each recorded video includes optional CC overlays showing which desktop flow action was running when the frame was recorded.
- CC use the real action log metadata from the run (aligned with the logs infrastructure described in the action‑log documentation).
- This functionality enables users to understand not only what visually happened, but also what the flow thought it was doing at each moment.
Scenarios this feature improves
- UI element not found or not visible at runtime
- Unexpected Windows security prompts or pop‑ups
- Timing or race condition issues
- Third‑party app behavior differing from attended versus unattended mode
- Regression detection after environment or OS updates
- Complex flows where textual logs alone are insufficient
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.