Skip to content

Commit 5ecd4ea

Browse files
authored
minor text edits
1 parent ba632df commit 5ecd4ea

1 file changed

Lines changed: 3 additions & 5 deletions

File tree

support/power-platform/power-automate/flow-run-issues/triggers-troubleshoot.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ After you fix the problem, edit the flow and then save it. You can then edit it
5757

5858
### Check for broken connections
5959

60-
Normally, you only need to sign in to a connection once, and you can keep using it until an admin removes it. However, connections break in the following situations:
60+
Normally, you only need to sign in to a connection once, and you can keep using it until an admin removes it. However, connections might break in the following situations:
6161

6262
- The password for the connection expires.
6363
- Your organization has a policy that makes the connector's authentication token expire after a certain amount of time.
@@ -93,8 +93,6 @@ For more information on available plans, see [Power Automate plans](https://make
9393

9494
### Determine whether trigger check is skipped
9595

96-
Locate the flow's trigger conditions and verify that the condition expressions correctly and accurately reflect your requirements.
97-
9896
To check for skipped trigger runs:
9997

10098
1. Sign in to [Power Automate](https://make.powerautomate.com).
@@ -103,11 +101,11 @@ To check for skipped trigger runs:
103101

104102
:::image type="content" source="./media/triggers-troubleshoot/all-runs.png" alt-text="The 28-day run history view showing all runs." lightbox="media/triggers-troubleshoot/all-runs.png":::
105103

106-
If a run was expected but didn't happen, look for the specific run to see if the trigger check was skipped. A skipped check means the condition was false, and the flow wasn't initiated. [Review the flow's inputs and trigger conditions](#review-flow-inputs-and-trigger-conditions) to confirm they align with your expectations. You might need to adjust the condition expression to fix the issue.
104+
If a run was expected but didn't happen, look for the specific run to see if the trigger check was skipped. A skipped check means the trigger condition wasn't met, and the flow wasn't initiated. [Review the flow's inputs and trigger conditions](#review-flow-inputs-and-trigger-conditions) to confirm they align with your expectations. You might need to adjust the condition expression to fix the issue.
107105

108106
### Review flow inputs and trigger conditions
109107

110-
Follow these steps to review your inputs and conditions:
108+
Locate the flow's trigger conditions and verify that the condition expressions correctly and accurately reflect your requirements. Follow these steps to review your inputs and conditions:
111109

112110
> [!NOTE]
113111
> You can use either the [new designer](/power-automate/flows-designer) or the classic designer to configure and review your cloud flow. The steps are similar in both designers. For more information, see [Identify differences between the new designer and the classic designer](/power-automate/flows-designer#identify-differences-between-the-new-designer-and-the-classic-designer).

0 commit comments

Comments
 (0)