From bcb7dacb99477a27316c1f3c4a132868a614d9f2 Mon Sep 17 00:00:00 2001
From: Ashton Huxtable <78318468+ashton-huxtable@users.noreply.github.com>
Date: Thu, 31 Oct 2024 14:12:54 -0600
Subject: [PATCH] Add FAQ on omitted properties

---
 src/protocols/faq.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/protocols/faq.md b/src/protocols/faq.md
index d91b5cdb6e..fedfe06638 100644
--- a/src/protocols/faq.md
+++ b/src/protocols/faq.md
@@ -148,6 +148,10 @@ That being said, there are plenty of scenarios where the reactive Schema functio
 
 Blocked events are blocked from sending to all Segment Destinations, including warehouses and streaming Destinations. When an Event is blocked using a Tracking Plan, it does not count towards your MTU limit. They will, however, count toward your MTU limit if you enable [blocked event forwarding](/docs/protocols/enforce/forward-blocked-events/) in your Source settings.
 
+### If I omit unplanned properties or properties that generate JSON schema violations, what happens to them?
+
+Properties that are omitted due to JSON Schema Violations or being unplanned are not stored in Segment logs. Segment only stores fully blocked events for 30 days. Omitted properties are dropped from the events and can only be found in the `context.violations` object of an event payload. If Violations are forwarded to a new source, then the omitted properties can also be seen in the Violation Generated event under `violationField` in the `properties` object of the event. 
+
 ### Why am I seeing unplanned properties/traits in the payload when violations are triggered, despite using schema controls to omit them?
 
 If you're seeing unplanned properties/traits in your payload despite using Schema Controls, you might want to select a new degree of blocking controls.