You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/logic-apps/quickstart-create-logic-apps-visual-studio-code.md
+33-34Lines changed: 33 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -270,19 +270,19 @@ In Visual Studio Code, you can open and review the earlier versions for your log
270
270
271
271
:::image type="content" source="media/quickstart-create-logic-apps-visual-studio-code/view-previous-versions.png" alt-text="Screenshot that shows Visual Studio Code and a logic app's earlier versions.":::
272
272
273
-
1. To view an earlier version, select either step:
273
+
1. To view an earlier version, choose one of the following steps:
274
274
275
-
* To view the JSON definition, under **Versions**, select the version number for that definition. Or, open that version's shortcut menu, and select **Open in Editor**.
275
+
- To view the JSON definition, under **Versions**, select the version number for that definition. Or, from the version shortcut menu, select **Open in Editor**.
276
276
277
277
A new file opens on your local computer and shows that version's JSON definition.
278
278
279
-
* To view the version in the read-only designer view, open that version's shortcut menu, and select **Open in Designer**.
279
+
- To view the version in the read-only designer, from the version's shortcut menu, select **Open in Designer**.
280
280
281
281
1. To promote an earlier version to the current version, follow these steps:
282
282
283
-
1. Under **Versions**, open the earlier version's shortcut menu, and select **Promote**.
283
+
1. Under **Versions**, from the earlier version's shortcut menu, select **Promote**.
284
284
285
-

285
+
:::image type="content" source="media/quickstart-create-logic-apps-visual-studio-code/promote-earlier-version.png" alt-text="Screenshot that shows Visual Studio Code and how to promote an earlier logic app version to the current version. ":::
286
286
287
287
1. To continue after Visual Studio Code prompts you for confirmation, select **Yes**.
288
288
@@ -292,65 +292,64 @@ In Visual Studio Code, you can open and review the earlier versions for your log
292
292
293
293
## Disable or enable logic apps
294
294
295
-
In Visual Studio Code, if you edit a published logic app workflow and save your changes, you *overwrite* your already deployed app. To avoid breaking your logic app workflow in production and minimize disruption, disable your logic app resource first. You can then reactivate your logic app after you confirm that your logic app still works.
295
+
In Visual Studio Code, if you edit a published logic app workflow and save your changes, you *overwrite* your already deployed logic app. To avoid breaking your logic app workflow in production and minimize disruption, disable your logic app resource first. After you confirm the workflow still functions as expected, you can reactivate the logic app resource.
296
296
297
-
Disabling or enabling a logic app affects workflow instances in the following ways:
297
+
Disabling or enabling a logic app resource affects workflow instances in the following ways:
298
298
299
-
* Azure Logic Apps continues all in-progress and pending runs until they finish. Based on the volume or backlog, this process might take time to complete.
299
+
- Azure Logic Apps continues in-progress and pending workflow runs until they finish. Based on the volume or backlog, this process might take time to complete.
300
300
301
-
* Azure Logic Apps doesn't create or run new workflow instances.
301
+
- Azure Logic Apps doesn't create or run new workflow instances.
302
302
303
-
* The trigger won't fire the next time that its conditions are met.
303
+
- The trigger doesn't fire the next time that its conditions are met.
304
304
305
-
* The trigger state remembers the point at which the logic app was stopped. So, if you reactivate the logic app, the trigger fires for all the unprocessed items since the last run.
305
+
- The trigger state remembers the point where the workflow stopped. So, if you reactivate the logic app, the trigger fires for any items not yet processed since the last run.
306
306
307
-
To stop the trigger from firing on unprocessed items since the last run, clear the trigger's state before you reactivate the logic app:
307
+
To stop the trigger from firing on these unprocessed items, before you reactivate the logic app resource, clear the trigger state:
308
308
309
-
1. In the logic app, edit any part of the workflow's trigger.
309
+
1. In the workflow, edit any part of the trigger.
310
310
1. Save your changes. This step resets your trigger's current state.
311
-
1. Reactivate your logic app.
311
+
1. Reactivate your logic app resource.
312
312
313
-
* When a workflow is disabled, you can still resubmit runs.
313
+
- When the logic app resource is disabled, you can still resubmit workflow runs.
314
314
315
-
To disable or enable a logic app in Visual Studio Code, follow these steps:
315
+
To disable or enable a logic app resource in Visual Studio Code, follow these steps:
316
316
317
-
1.Sign in to your Azure account and subscription from [inside Visual Studio Code](#access-azure), if you haven't already.
317
+
1.In Visual Studio Code, open the Azure window.
318
318
319
-
1. In the Azure window, under **Logic Apps**, expand your Azure subscription so that you can view all the logic apps in that subscription.
319
+
1. In the **Logic Apps (Consumption)** section, expand your Azure subscription to view the associated logic apps.
320
320
321
-
1. To disable the logic app that you want, open the logic app menu, and select **Disable**.
321
+
1. To disable a logic app resource, from the logic app shortcut menu, select **Disable**.
322
322
323
-

323
+
:::image type="content" source="media/quickstart-create-logic-apps-visual-studio-code/disable-published-logic-app.png" alt-text="Screenshot that shows Visual Studio Code and how to disable a logic app resource.":::
324
324
325
-
1. When you're ready to reactivate your logic app, open the logic app menu, and select **Enable**.
325
+
1. When you're ready to reactivate the logic app resource, from the logic app shortcut menu, select **Enable**.
326
326
327
-

327
+
:::image type="content" source="media/quickstart-create-logic-apps-visual-studio-code/enable-published-logic-app.png" alt-text="Screenshot that shows Visual Studio Code and how to enable a logic app resource.":::
328
328
329
329
<aname="delete-logic-apps"></a>
330
330
331
331
## Delete logic apps
332
332
333
333
Deleting a logic app affects workflow instances in the following ways:
334
334
335
-
* Azure Logic Apps makes a best effort to cancel any in-progress and pending runs.
335
+
- Azure Logic Apps makes a best effort to cancel any in-progress and pending workflow runs.
336
336
337
-
Even with a large volume or backlog, most runs are canceled before they finish or start. However, the cancellation process might take time to complete. Meanwhile, some runs might get picked up for execution while the service works through the cancellation process.
337
+
Even with a large volume or backlog, most runs are canceled before they finish or start. However, the cancelation process might take time to complete. Meanwhile, some runs might get picked up for execution while the service works through the cancelation process.
338
338
339
-
* Azure Logic Apps doesn't create or run new workflow instances.
339
+
- Azure Logic Apps doesn't create or run new workflow instances.
340
340
341
-
* If you delete a workflow and then recreate the same workflow, the recreated workflow has different metadata. You have to resave any workflow that called the deleted workflow. That way, the caller gets the correct information for the recreated workflow. Otherwise, calls to the recreated workflow fail with an `Unauthorized` error. This behavior also applies to workflows that use artifacts in integration accounts and workflows that call Azure functions.
341
+
- If you delete a workflow and then recreate the same workflow, the recreated workflow has different metadata. You need to resave any workflow that called the deleted workflow. That way, the caller gets the correct information for the recreated workflow. Otherwise, calls to the recreated workflow fail with an `Unauthorized` error. This behavior also applies to workflows that use artifacts in integration accounts and workflows that call Azure functions.
342
342
343
-
To delete a logic app in Visual Studio Code, follow these steps:
343
+
To delete a logic app resource from Visual Studio Code, follow these steps:
344
344
345
-
1.Sign in to your Azure account and subscription from [inside Visual Studio Code](#access-azure), if you haven't already.
345
+
1.In Visual Studio Code, open the Azure window.
346
346
347
-
1. In the Azure window, under **Logic Apps**, expand your Azure subscription so that you can view all the logic apps in that subscription.
347
+
1. In the **Logic Apps (Consumption)** section, expand your Azure subscription to view the associated logic app resources. Find the logic app resource you want to delete.
348
348
349
-
1.Find the logic app that you want to delete, open the logic app menu, and select **Delete**.
349
+
1.From the logic app shortcut menu, select **Delete**.
350
350
351
-

351
+
:::image type="content" source="media/quickstart-create-logic-apps-visual-studio-code/delete-logic-app.png" alt-text="Screenshot that shows Visual Studio Code and how to delete a logic app resource.":::
352
352
353
-
## Next steps
353
+
## Related content
354
354
355
-
> [!div class="nextstepaction"]
356
-
> [Create Standard single-tenant logic app workflows in Visual Studio Code](../logic-apps/create-standard-workflows-visual-studio-code.md)
355
+
-[Create Standard workflows in single-tenant Azure Logic Apps by using Visual Studio Code](../logic-apps/create-standard-workflows-visual-studio-code.md)
0 commit comments