|
1 | 1 | --- |
2 | 2 | title: Handle version control error when saving as draft or publishing a flow in an unmodified context when there is an unpublished active row |
3 | 3 | description: Provides a resolution for the attempting to do a published update of a component in an unmodified context when there is an unpublished active row error when using version control in Power Automate for desktop. |
4 | | -author: Nikos.Moutzourakis |
5 | | -ms.author: Nikos.Moutzourakis |
| 4 | +ms.reviewer: Nikos.Moutzourakis, v-shaywood |
6 | 5 | ms.date: 11/13/2025 |
7 | 6 | ms.custom: sap:Desktop flows\Power Automate for desktop errors |
8 | 7 | --- |
9 | | -# Handle version control error when saving as draft or publishing a flow in an unmodified context when there is an unpublished active row |
| 8 | + |
| 9 | +# Version control error when publishing a flow or saving it as a draft |
| 10 | + |
| 11 | +This article provides troubleshooting guidance for an error you might encounter in Power Automate for Desktop when publishing a flow or saving it as a draft in an unmodified context when there is an unpublished active row. This issue can occur when the *Desktop flow version control* feature is enabled. For more information about the version control feature, see [Version control in Power Automate for desktop](/power-automate/desktop-flows/version-control) |
10 | 12 |
|
11 | 13 | ## Symptoms |
12 | | -When saving as draft or publishing a flow, you see the error: |
13 | 14 |
|
14 | | -> “You are attempting to do a published update of a component in an unmodified context when there is an unpublished active row.” |
| 15 | +After you enable version control for desktop flows, when you attempt to publish a flow or save it as a draft, you receive the following error message: |
| 16 | + |
| 17 | +> You are attempting to do a published update of a component in an unmodified context when there is an unpublished active row. |
15 | 18 |
|
16 | 19 | ## Cause |
17 | | -This error typically occurs in these scenarios: |
| 20 | + |
| 21 | +This error can occur in the following scenarios: |
| 22 | + |
18 | 23 | - You created or edited the flow using a newer version of Power Automate for Desktop, but your device is running an older version. |
19 | | -- The newer version is still rolling out and isn’t yet available on your device. |
20 | | -- You switched environments, and one of them doesn’t have version control enabled. |
| 24 | +- A newer version of Power Automate for Desktop is still rolling out and isn’t available on your device yet. |
| 25 | +- You switch from an environment that has version control enabled to one that doesn't. |
21 | 26 |
|
22 | 27 | ## Resolution |
23 | | -- Use the same version of Power Automate for Desktop that you last used to create or edit the flow, or upgrade to the latest version. |
24 | | -- If the newer version isn’t available yet, wait until the rollout completes. |
25 | | -- Ensure that version control is enabled in all environments where you edit or publish flows. |
| 28 | + |
| 29 | +1. Use the same version of Power Automate for Desktop that you previously used to create or edit the flow, or upgrade to the latest version. |
| 30 | +2. If a newer version of Power Automate for Desktop isn’t available on your device yet, wait for the rollout to complete. |
| 31 | +3. Ensure that version control is enabled for all environments where you edit or publish flows. |
0 commit comments