From 7d5f9f829bf52c6be5907bb8e8525b468c8418f5 Mon Sep 17 00:00:00 2001
From: vanand17 <96406241+vanand17@users.noreply.github.com>
Date: Fri, 27 Dec 2024 17:46:48 +1100
Subject: [PATCH 1/2] Update test a destination action

---
 src/connections/destinations/actions.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md
index 040d47fd55..91ad4b2f8b 100644
--- a/src/connections/destinations/actions.md
+++ b/src/connections/destinations/actions.md
@@ -163,7 +163,11 @@ You can also test within the mapping itself. To test the mapping:
 1. Navigate to the **Mappings** tab of your destination. 
 2. Select a mapping and click the **...** and select **Edit Mapping**. 
 3. In step 2 of the mappings edit page, click **Load Test Event from Source** to add a test event from the source, or you can add your own sample event. 
-4. Scroll to step 4 on the page, and click **Test Mapping** to test the mapping and view the response from the destination. 
+4. Scroll to step 4 on the page, and click **Test Mapping** to test the mapping and view the response from the destination.
+
+
+   >info ""
+   >The mechanism that allows that feature to pull an event from the pipeline only holds a small subset at a time and may not always find the event you're looking for. When that happens you can simply navigate to your source debugger, find an event to test with, copy that raw event, and paste the event into the Add test event interface.  
 
 ## Customize mappings
 

From 330059d819c3496a2409ba4d7dbc2661fc1300a9 Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Thu, 9 Jan 2025 11:16:11 -0500
Subject: [PATCH 2/2] Update src/connections/destinations/actions.md

---
 src/connections/destinations/actions.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md
index 91ad4b2f8b..7ace9ff38c 100644
--- a/src/connections/destinations/actions.md
+++ b/src/connections/destinations/actions.md
@@ -166,8 +166,8 @@ You can also test within the mapping itself. To test the mapping:
 4. Scroll to step 4 on the page, and click **Test Mapping** to test the mapping and view the response from the destination.
 
 
-   >info ""
-   >The mechanism that allows that feature to pull an event from the pipeline only holds a small subset at a time and may not always find the event you're looking for. When that happens you can simply navigate to your source debugger, find an event to test with, copy that raw event, and paste the event into the Add test event interface.  
+> info "Test Mapping might not return the events you're looking for"
+> Segment only surfaces a small subset of events for the Test Mapping feature and might not always return the event you're looking for. If you'd like to test with a specific event, copy a specific event from your [Source Debugger](/docs/connections/sources/debugger/) and paste it into the **Add test event** interface.
 
 ## Customize mappings