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/manage-logic-apps-with-azure-portal.md
+13-16Lines changed: 13 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,15 +133,15 @@ Deployed Consumption and Standard logic apps have different ways to disable and
133
133
134
134
#### Considerations for disabling a deployed Consumption logic app
135
135
136
-
Stopping a Consumption logic app affects all workflow instances in the following ways:
136
+
Disabling a Consumption logic app affects all workflow instances in the following ways:
137
137
138
138
* Azure Logic Apps continues all in-progress and pending workflow instances until they finish running. Based on the volume or backlog, this process might take time to complete.
139
139
140
140
* Azure Logic Apps doesn't create or run new workflow instances.
141
141
142
-
* You can resubmit workflow runs while the logic app is stopped.
142
+
* You can resubmit workflow runs while the logic app is disabled.
143
143
144
-
* The workflow trigger doesn't fire while the logic app is stopped. However, the trigger state remembers the point where you stopped the logic app. When you restart the logic app, the trigger fires for all unprocessed items since the last workflow run.
144
+
* The workflow trigger doesn't fire while the logic app is disabled. However, the trigger state remembers the point where you disabled the logic app. When you restart the logic app, the trigger fires for all unprocessed items since the last workflow run.
145
145
146
146
To stop the trigger from firing on all unprocessed items since the last workflow run, you must [clear the trigger state](#post-stoppage).
147
147
@@ -172,28 +172,28 @@ You can stop, start, or restart a Standard logic app, which affects all workflow
172
172
173
173
Stopping a Standard logic app versus disabling a child workflow have different effects, so review the following considerations before you continue:
174
174
175
-
-[Considerations for stopping Standard logic apps](#considerations-stop-standard-logic-apps)
175
+
-[Considerations for disabling Standard logic apps](#considerations-stop-standard-logic-apps)
176
176
-[Considerations for disabling a Standard workflow](#considerations-disable-enable-standard-workflows)
#### Considerations for stopping Standard logic apps
180
+
#### Considerations for disabling Standard logic apps
181
181
182
-
Stopping a Standard logic app affects all its workflow instances in the following ways:
182
+
Disabling a Standard logic app affects all its workflow instances in the following ways:
183
183
184
184
* Azure Logic Apps immediately cancels all in-progress and pending workflow runs.
185
185
186
186
* Azure Logic Apps doesn't create or run new workflow instances.
187
187
188
-
* You can resubmit workflow runs while the logic app is stopped.
188
+
* You can resubmit workflow runs while the logic app is disabled.
189
189
190
-
* Workflow triggers don't fire while the logic app is stopped. However, the trigger states remember the point where you stopped the logic app. When you restart the logic app, the triggers fire for all unprocessed items since the last time that the corresponding workflows ran.
190
+
* Workflow triggers don't fire while the logic app is disabled. However, the trigger states remember the point where you disabled the logic app. When you re-enable the logic app, the triggers fire for all unprocessed items since the last time that the corresponding workflows ran.
191
191
192
192
To stop the triggers from firing on all unprocessed items since the last time that the workflows ran, you must [clear the trigger state for each workflow](#post-stoppage).
193
193
194
194
<aname="disable-enable-standard-logic-apps"></a>
195
195
196
-
#### Disable or enable a deployed Standard logic app
196
+
#### Disable or enable deployed Standard logic apps
197
197
198
198
You can disable or enable one or multiple Standard logic apps at the same time.
199
199
@@ -214,7 +214,7 @@ You can disable or enable one or multiple Standard logic apps at the same time.
214
214
215
215
<aname="restart-standard-logic-app"></a>
216
216
217
-
#### Restart a deployed Standard logic app without stopping
217
+
#### Restart a deployed Standard logic app without disabling
218
218
219
219
You can restart a single Standard logic app at any time.
220
220
@@ -228,7 +228,7 @@ You can restart a single Standard logic app at any time.
#### Considerations for disabling a Standard workflow
231
+
#### Considerations for disabling Standard workflows
232
232
233
233
Disabling a workflow affects all its workflow instances in the following ways:
234
234
@@ -255,19 +255,16 @@ Disabling a workflow affects all its workflow instances in the following ways:
255
255
256
256
* You can resubmit workflow runs while the workflow is disabled.
257
257
258
-
* The workflow trigger doesn't fire while the logic app is stopped or the workflow is disabled. However, the trigger state remembers the point where you disabled the workflow. When you restart the logic app or re-enable the workflow, the trigger fires for all unprocessed items since the last workflow run.
258
+
* The workflow trigger doesn't fire while the logic app or workflow is disabled. However, the trigger state remembers the point where you disabled the workflow. When you restart the logic app or enable the workflow, the trigger fires for all unprocessed items since the last workflow run.
259
259
260
260
To stop the trigger from firing on all unprocessed items since the last workflow run, you must [clear the trigger state](#post-stoppage).
261
261
262
262
<aname="disable-enable-standard-workflows"></a>
263
263
264
264
#### Disable or enable Standard workflows
265
265
266
-
#### Disable or enable a Standard workflow
267
-
268
266
To stop the trigger from firing the next time when the trigger condition is met, disable your workflow. You can disable or enable one or multiple Standard logic apps at the same time.
269
267
270
-
271
268
1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
272
269
273
270
1. On the logic app menu, under **Workflows**, select **Workflows**.
@@ -487,7 +484,7 @@ To recover a deleted Standard logic app that uses the **Workflow Service Plan**
487
484
488
485
1. In the [Azure portal](https://portal.azure.com), create a new Standard logic app resource with the same hosting option and pricing tier. You can use either a new name or reuse the name from the deleted logic app.
489
486
490
-
1. Before you continue, [stop the new logic app](#disable-or-enable-a-deployed-standard-logic-app).
487
+
1. Before you continue, [disable the new logic app](#disable-enable-standard-logic-apps).
491
488
492
489
1. On the logic app menu, under **Settings**, select **Environment variables**. On the **App settings** tab, update the following values. Make sure to save your changes when you finish.
0 commit comments