An EventRejection captures an event that the platform declined to accept onto the bus, so problems are visible rather than silent. Each rejection names the topicName it targeted and the producerSlug that emitted it, along with a reason describing what went wrong and an optional fieldPath pointing to the specific part of the payload that failed validation. The rejectedAt timestamp records when it happened. Together these let teams diagnose why a product's events are not flowing — typically a schema mismatch or an unauthorized producer.
Technical section
Data model, API, and internals — visible to developers.