Skip to content

Commit 53e82e6

Browse files
Merge pull request #219180 from kromerm/debug
Update concepts-data-flow-debug-mode.md
2 parents 727f915 + 95229ff commit 53e82e6

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/data-factory/concepts-data-flow-debug-mode.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: data-factory
88
ms.subservice: data-flows
99
ms.topic: conceptual
1010
ms.custom: synapse
11-
ms.date: 07/12/2022
11+
ms.date: 11/21/2022
1212
---
1313

1414
# Mapping data flow Debug Mode
@@ -42,6 +42,9 @@ In most cases, it's a good practice to build your Data Flows in debug mode so th
4242
> [!NOTE]
4343
> Every debug session that a user starts from their browser UI is a new session with its own Spark cluster. You can use the monitoring view for debug sessions above to view and manage debug sessions. You are charged for every hour that each debug session is executing including the TTL time.
4444
45+
This video clip talks about tips, tricks, and good practices for data flow debug mode
46+
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RWQK3m]
47+
4548
## Cluster status
4649

4750
The cluster status indicator at the top of the design surface turns green when the cluster is ready for debug. If your cluster is already warm, then the green indicator will appear almost instantly. If your cluster wasn't already running when you entered debug mode, then the Spark cluster will perform a cold boot. The indicator will spin until the environment is ready for interactive debugging.

0 commit comments

Comments
 (0)