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: support/power-platform/power-automate/connections/troubleshoot-broken-connections.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ This article describes the following common issues about broken connections in M
24
24
25
25
## Connection times out
26
26
27
-
This issue occurs when a client (such as a web browser or an application) tries to establish a connection with a server, but the server doesn't respond within a specified time limit. This can occur for various reasons, such as the server being offline, network issues, or the server taking too long to process the request. When the connection times out, the client stops waiting for a response and terminates the connection attempt.
27
+
This issue occurs when a client (such as a web browser or an application) tries to establish a connection with a server, but the server doesn't respond within a specified time limit. This can occur for several reasons, such as the server being offline, network issues, or the server taking too long to process the request. When the connection times out, the client stops waiting for a response and terminates the connection attempt.
28
28
29
29
You might also receive the following error message:
30
30
@@ -48,11 +48,11 @@ When a DLP block occurs, you might also receive one of the following error messa
48
48
### Troubleshooting steps
49
49
50
50
1. Review DLP policies: Check the DLP policies configured in the organization to understand what actions are being blocked and why.
51
-
2. Consult with your administrator: There might be a chance that the administrator has blocked the particular connector or connection. It's a good idea to consult with them and discuss the issue to unblock it.
51
+
2. Consult with your administrator: There might be a chance that the administrator blocked the connector or connection. It's a good idea to consult with them and discuss the issue to unblock it.
52
52
53
53
## Invalid authenticated devices
54
54
55
-
This refers to a situation where a user tries to authenticate using a device for multi-factor authentication (MFA), but the device has been disabled. This issue isn't related to Power Automate but rather to the tenant's configuration at the administrative level.
55
+
This refers to a situation where a user tries to authenticate using a device for multi-factor authentication (MFA), but the device is disabled. This issue isn't related to Power Automate but rather to the tenant's configuration at the administrative level.
56
56
57
57
In this situation, you might also receive one of the following error messages:
58
58
@@ -68,7 +68,7 @@ In this situation, you might also receive one of the following error messages:
68
68
69
69
## Inactivity for a long time
70
70
71
-
This refers to a situation where a connection becomes invalid because it hasno't been used for a specified period. For example, the SharePoint connector requires usage at least once every 90 days to remain active. If the connection isn't used within this period, it will expire.
71
+
This refers to a situation where a connection becomes invalid because it hasn't been used for a specified period. For example, the SharePoint connector requires usage at least once every 90 days to remain active. If the connection isn't used within this period, it will expire.
72
72
73
73
In this situation, you might also receive one of the following error messages:
74
74
@@ -87,11 +87,11 @@ This refers to problems that occur when a user tries to use features that requir
87
87
88
88
### Troubleshooting steps
89
89
90
-
Ensure the user has the correct license to interact with the system as required in attended mode. For more information, see [Which Power Automate licenses do I need?](/power-platform/admin/power-automate-licensing/faqs#which-power-automate-licenses-do-i-need).
90
+
Ensure the user has the correct license to interact with the system as required in attended mode. For more information, see [Which Power Automate licenses do I need?](/power-platform/admin/power-automate-licensing/faqs#which-power-automate-licenses-do-i-need)
91
91
92
92
## Password modification by a user
93
93
94
-
This issue occurs when the account password used to create the connection is deleted, changed, or expired. Since account verification is a crucial part of authentication whenever a connection is triggered, the connection will break if new password isn't updated. To avoid this issue, use services like [Microsoft Entra ID](/entra/fundamentals/whatis).
94
+
This issue occurs when the account password used to create the connection is deleted, changed, or expired. Since account verification is a crucial part of authentication whenever a connection is triggered, the connection will break if the new password isn't updated. To avoid this issue, use services like [Microsoft Entra ID](/entra/fundamentals/whatis).
95
95
96
96
You might also receive the following error message:
97
97
@@ -115,7 +115,7 @@ Contact the tenant administrator to understand the specific changes and reauthor
115
115
116
116
## Connection owner account is deleted or disabled
117
117
118
-
This refers to a situation where the account that created a connection is either removed or disabled in the directory. As a result, the connection becomes invalid, affecting all users who shared it.
118
+
This refers to a situation where the account that created a connection is either removed or disabled in the directory. As a result, the connection becomes invalid, affecting all users who share it.
119
119
120
120
In this situation, you might also receive one of the following error messages:
0 commit comments