Skip to content

Commit ce25043

Browse files
committed
Resave parent after recreating child warning
1 parent 5e3e307 commit ce25043

File tree

3 files changed

+12
-0
lines changed

3 files changed

+12
-0
lines changed

articles/logic-apps/ise-manage-integration-service-environment.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -173,6 +173,10 @@ Before you delete an ISE that you no longer need or an Azure resource group that
173173

174174
After you delete your ISE, you might have to wait up to 9 hours before you try to delete your Azure virtual network or subnets.
175175

176+
> [!NOTE]
177+
> If you delete and recreate a child logic app, you must then resave its parent logic app. This is because the deleted and recreated child apps will have different metadata.
178+
> If you don't resave the parent logic app after recreating its child, your calls to the child logic app will fail with an error of "unauthorized." This applies to parent-child logic apps that use artifacts in integration accounts, call Azure functions, and so on.
179+
176180
## Next steps
177181

178182
* [Add resources to integration service environments](../logic-apps/add-artifacts-integration-service-environment-ise.md)

articles/logic-apps/manage-logic-apps-with-azure-portal.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -141,6 +141,10 @@ Deleting your logic app affects your workflow instances in these ways:
141141

142142
* The Logic Apps engine won't create or run new workflow instances.
143143

144+
> [!NOTE]
145+
> If you delete and recreate a child logic app, you must then resave its parent logic app. This is because the deleted and recreated child apps will have different metadata.
146+
> If you don't resave the parent logic app after recreating its child, your calls to the child logic app will fail with an error of "unauthorized." This applies to parent-child logic apps that use artifacts in integration accounts, call Azure functions, and so on.
147+
144148
<a name="delete-single-logic-app"></a>
145149

146150
### Delete single logic app

articles/logic-apps/manage-logic-apps-with-visual-studio.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -264,6 +264,10 @@ To delete your logic app from the Azure portal, in Cloud Explorer, open your log
264264
> When you delete a logic app, no new runs are instantiated. All in-progress and pending runs are canceled.
265265
> If you have thousands of runs, cancellation might take significant time to complete.
266266
267+
> [!NOTE]
268+
> If you delete and recreate a child logic app, you must then resave its parent logic app. This is because the deleted and recreated child apps will have different metadata.
269+
> If you don't resave the parent logic app after recreating its child, your calls to the child logic app will fail with an error of "unauthorized." This applies to parent-child logic apps that use artifacts in integration accounts, call Azure functions, and so on.
270+
267271
## Troubleshooting
268272

269273
When you open your logic app project in the Logic Apps Designer, you might not get the option for selecting your Azure subscription. Instead, your logic app opens with an Azure subscription that's not the one you want to use. This behavior happens because after you open a logic app's .json file, Visual Studio caches the first selected subscription for future use. To resolve this problem, try one of these steps:

0 commit comments

Comments
 (0)