Skip to content

Commit b6f8f2e

Browse files
20250227 ms.topic pass
1 parent fb4e1cc commit b6f8f2e

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

articles/synapse-analytics/spark/apache-spark-handle-livy-error.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Handle Livy errors on Apache Spark in Synapse
33
description: Learn how to handle and interpret job failures on Apache Spark in Synapse Analytics.
44
author: Niharikadutta
55
ms.service: azure-synapse-analytics
6-
ms.topic: overview
6+
ms.topic: error-reference
77
ms.subservice: spark
88
ms.date: 08/29/2022
99
ms.author: nidutta

articles/synapse-analytics/sql/resources-self-help-sql-on-demand.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article contains information that can help you troubleshoot pr
44
author: azaricstefan
55
ms.author: stefanazaric
66
ms.reviewer: whhender, wiassaf
7-
ms.topic: overview
7+
ms.topic: troubleshooting-known-issue
88
ms.service: azure-synapse-analytics
99
ms.subservice: sql
1010
ms.date: 09/26/2024

articles/synapse-analytics/troubleshoot/troubleshoot-synapse-studio-and-storage-connectivity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: Danzhang-msft
55
ms.author: danzhang
66
ms.service: azure-synapse-analytics
77
ms.subservice: troubleshooting
8-
ms.topic: conceptual
8+
ms.topic: troubleshooting-problem-resolution
99
ms.date: 02/15/2022
1010
ms.reviewer: whhender
1111
---

articles/synapse-analytics/troubleshoot/troubleshoot-synapse-studio.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Troubleshoot Synapse Studio
33
description: Troubleshoot Synapse Studio
44
author: JeneZhang
55
ms.service: azure-synapse-analytics
6-
ms.topic: conceptual
6+
ms.topic: troubleshooting-known-issue
77
ms.subservice: troubleshooting
88
ms.date: 10/01/2023
99
ms.author: jingzh
@@ -24,7 +24,7 @@ In some cases, if your browser session has been inactive for an extended period,
2424

2525
### Root cause and mitigation
2626

27-
Handling token expiration in Synapse Studio requires careful consideration, especially when working in a live workspace without Git integration. Heres 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:
2828
- **With Git integration:**
2929
- Regularly commit your changes. This ensures that even if you need to refresh your browser to renew your session, your work is safely stored.
3030
- 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
144144

145145
+ 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.
146146

147-
+ If you can run notebook on a different workstation but in the same network environment, please ensure you didnt 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.
148148

149149
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:
150150

@@ -155,7 +155,7 @@ wss://{workspace}.dev.azuresynapse.net/{path}
155155

156156
+ **{path}** indicates any sub-path (i.e., slash character is included) in URI.
157157

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.
159159

160160
## Message queue full or is completed and cannot accept more items
161161

0 commit comments

Comments
 (0)