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/synapse-analytics/troubleshoot/troubleshoot-synapse-studio.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Troubleshoot Synapse Studio
3
3
description: Troubleshoot Synapse Studio
4
4
author: JeneZhang
5
5
ms.service: azure-synapse-analytics
6
-
ms.topic: conceptual
6
+
ms.topic: troubleshooting-known-issue
7
7
ms.subservice: troubleshooting
8
8
ms.date: 10/01/2023
9
9
ms.author: jingzh
@@ -24,7 +24,7 @@ In some cases, if your browser session has been inactive for an extended period,
24
24
25
25
### Root cause and mitigation
26
26
27
-
Handling token expiration in Synapse Studio requires careful consideration, especially when working in a live workspace without Git integration. Here’s how to manage your session to avoid losing work:
27
+
Handling token expiration in Synapse Studio requires careful consideration, especially when working in a live workspace without Git integration. Here's how to manage your session to avoid losing work:
28
28
-**With Git integration:**
29
29
- Regularly commit your changes. This ensures that even if you need to refresh your browser to renew your session, your work is safely stored.
30
30
- After committing, you can refresh your browser to reset the session and then continue to publish your changes.
@@ -144,7 +144,7 @@ If possible, please try to switch your network environment, such as inside/outsi
144
144
145
145
+ If you can run notebook on the same workstation but in a different network environment, please work with your network administrator to find out whether the WebSocket connection has been blocked.
146
146
147
-
+ If you can run notebook on a different workstation but in the same network environment, please ensure you didn’t install any browser plugin that may block the WebSocket request.
147
+
+ If you can run notebook on a different workstation but in the same network environment, please ensure you didn't install any browser plugin that may block the WebSocket request.
148
148
149
149
Otherwise, please contact your network administrator and ensure the outbound WebSocket requests with the following URL pattern is allowed and their request header is not redacted:
+**{path}** indicates any sub-path (i.e., slash character is included) in URI.
157
157
158
-
This URL pattern is looser than the one shown in “Root Cause” section because it allows for us adding new WebSocket-dependent features to Synapse without any potential connectivity issue in the future.
158
+
This URL pattern is looser than the one shown in "Root Cause" section because it allows for us adding new WebSocket-dependent features to Synapse without any potential connectivity issue in the future.
159
159
160
160
## Message queue full or is completed and cannot accept more items
0 commit comments