From e8480f8e4de24b575a57ba0014fa7203ee3995ce Mon Sep 17 00:00:00 2001
From: tanjinhong72 <82503411+tanjinhong72@users.noreply.github.com>
Date: Sat, 21 Jan 2023 13:44:36 +0800
Subject: [PATCH] Update debugger.md

---
 src/profiles/debugger.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/profiles/debugger.md b/src/profiles/debugger.md
index f4a70a9971..a7dca238d0 100644
--- a/src/profiles/debugger.md
+++ b/src/profiles/debugger.md
@@ -7,7 +7,7 @@ redirect_from:
 
 The Engage Source Debugger enables you to inspect and monitor events that Engage sends downstream
 
-Because Engage generates a unique Source for every Destination connected to a Space, the Debugger gives you insight into how Engage sends events before they reach their Destination.
+Because Engage generates a unique Source for every Destination connected to a Space, the Debugger gives you insight into how Engage sends events before they reach their Destination. This automatically generated source cannot be deleted even when the destination is removed, in order for Engage to function as designed. The source will be reused by Engage as needed.
 
 The Debugger provides you with the payload information you need to troubleshoot potential formatting issues and ensure Engage sends events as your Destinations expect.