|
| 1 | +--- |
| 2 | +title: Fix Desktop Flow Failures from Cache Issues |
| 3 | +description: Resolve desktop flow errors in Power Automate that occur because of corrupted or conflicting cache files. |
| 4 | +ms.reviewer: spanopoulos, v-shaywood |
| 5 | +ms.date: 01/15/2026 |
| 6 | +ms.custom: sap:Desktop flows |
| 7 | +--- |
| 8 | + |
| 9 | +# Desktop flows fail because of binary caching problems |
| 10 | + |
| 11 | +## Summary |
| 12 | + |
| 13 | +When you run desktop flows in Power Automate for desktop, the binary caching feature downloads and stores files locally to improve performance. Sometimes, these cached files can become corrupted or outdated, which prevents your flows from running correctly. |
| 14 | + |
| 15 | +If desktop flows triggered from the cloud don't run or behave as expected, or you receive errors about file conflicts or corrupted files, try clearing the cache folders as a first troubleshooting step. This guide helps you identify your machine runtime configuration and clear the appropriate cache folders. |
| 16 | + |
| 17 | +## Symptoms |
| 18 | + |
| 19 | +You experience one or more of the following problems: |
| 20 | + |
| 21 | +- Failed desktop flows that are triggered from the cloud |
| 22 | +- Error messages about file conflicts or corrupted files |
| 23 | +- Unexpected behavior during flow execution |
| 24 | + |
| 25 | +## Cause |
| 26 | + |
| 27 | +Binary caching stores files locally to optimize performance. Cache errors occur when: |
| 28 | + |
| 29 | +- Cache files become corrupted |
| 30 | +- Outdated files conflict with newer versions |
| 31 | +- Duplicate files exist in the cache directory |
| 32 | + |
| 33 | +## Solution |
| 34 | + |
| 35 | +Clear the cache folders on your computer. The cache folder location depends on your Power Automate machine runtime configuration. |
| 36 | + |
| 37 | +### Determine your configuration |
| 38 | + |
| 39 | +Identify which user account your service account for the Power Automate machine runtime is configured to use. |
| 40 | + |
| 41 | +1. On the Start menu, open the Power Automate machine runtime application. Or, open the Power Automate Console, and then select **Settings** > **Open machine settings**. |
| 42 | + |
| 43 | +1. On the **Troubleshoot** page, the **Service account** section shows the current configuration, including the domain and username. |
| 44 | + |
| 45 | + - **Default configuration**: The service account for the Power Automate machine runtime runs under the UIFlowService system account (`NT Service\UIFlowService`). |
| 46 | + - **Custom configuration**: The service account for the Power Automate machine runtime runs under a specific user account that you configured (`DOMAIN\Username`). |
| 47 | + |
| 48 | +### Clear cache for the default configuration (UIFlowService account) |
| 49 | + |
| 50 | +If your service account for the Power Automate machine runtime uses the default UIFlowService account configuration: |
| 51 | + |
| 52 | +1. In File Explorer, go to `C:\Windows\ServiceProfiles\UIFlowService\AppData\Local\Cache`. |
| 53 | +1. Delete both the `storage` and `metadata` folders. |
| 54 | +1. Restart the UIFlowService service: |
| 55 | + 1. Press <kbd>Win</kbd>+<kbd>R</kbd> to open the **Run** dialog box. |
| 56 | + 1. Type **services.msc**, and press <kbd>Enter</kbd>. |
| 57 | + 1. In the list, find and right-click **Power Automate Service**, and then select **Restart**. |
| 58 | + |
| 59 | +### Clear cache for a custom user configuration |
| 60 | + |
| 61 | +If your service account for the Power Automate machine runtime is configured to run under a custom user account: |
| 62 | + |
| 63 | +1. In File Explorer, go to `%LOCALAPPDATA%\Cache` or `C:\Users\<Username>\AppData\Local\Cache`. |
| 64 | + |
| 65 | + > [!NOTE] |
| 66 | + > By default, the AppData folder is hidden. To show it, open File Explorer, and then select **View** > **Show** > **Hidden items**. |
| 67 | +
|
| 68 | +1. Delete all files and folders in the Cache directory. |
| 69 | +1. Restart the **Power Automate Service** or restart your device. |
| 70 | + |
| 71 | +### Optional cache folders to clear |
| 72 | + |
| 73 | +If the problem persists, clear these additional folders: |
| 74 | + |
| 75 | +1. Under `%LOCALAPPDATA%\Microsoft\Power Automate Desktop`: |
| 76 | + - `Scripts`: Stores execution logs and cached data for cloud-triggered desktop flows. |
| 77 | + - `Console\Scripts`: Stores execution logs and cached data for flows that are triggered from Power Automate Desktop Console. |
| 78 | + - `Designer\Scripts`: Stores execution logs and cached data for flows that are triggered from Power Automate Desktop Designer. |
| 79 | + - `Cache\(MSI or MSIX)`: Safe to remove all folders except `Account` and the `msalcache.bin3` file. |
| 80 | + - Deleting these folders doesn't cause data loss, but you might see previously dismissed notifications again. |
| 81 | + - If you delete the `Account` folder and `msalcache.bin3` file, you're signed out of Power Automate Desktop. |
| 82 | + - `DesktopFlowModules`: Contains custom modules downloaded from the Asset Library. Missing modules are downloaded again at runtime. |
| 83 | +2. Under `C:\Windows\ServiceProfiles\UIFlowService\AppData\Local`: |
| 84 | + - `Microsoft\Power Automate Desktop\Cache`: Depending on your Power Automate Desktop version, some files might be cached here instead of the locations that are listed earlier in the previous sections. |
| 85 | + - `Users`: Contains additional intermediate files that are related to binary caching. To resolve further errors, clear this folder. |
| 86 | + - After you remove files from this path, restart **Power Automate Service** as described in the previous procedures. |
| 87 | + |
| 88 | +If clearing cache folders doesn't resolve the problem, contact [Power Automate support](https://www.microsoft.com/power-platform/products/power-automate/support/). |
0 commit comments