# Review and Resolve Event Violations

Upon connecting your Tracking Plan to a Source, you can to view violations grouped by event. To view violations, click on the Violations button located on the Schema tab in a Source. A filter can be applied to only show events with violations within the past hour, 24 hours, and 7 days.

* FREE: x
* TEAM: x
* BUSINESS: ✓
* ADDON: ✓

Protocols is available as an addon for Business plans only.

See the [available plans](https://segment.com/pricing), or [contact Support](https://segment.com/help/contact/)

![Violations summary page containing two Track events that have violations.](https://docs-resources.prod.twilio.com/ee4b0d81da933934daf2ff0e8235ee41a1fb2f6ceaac1726980a30e76f1fa05e.png)

To view detailed violations for an event, click on the specific event. Specific violations include:

* Missing required properties
* Invalid property value data types
* Property values that do not pass applied conditional filtering

In the event detail violations view, a filter can be applied to only show violations in the past hour, 24 hours, and 7 days.

![Checkout Started Violations showing properties.currency and properties.order\_id errors with counts and last seen times.](https://docs-resources.prod.twilio.com/73a43049df1f6da6ee6293700ac6867f97a6d104cc3e91d932164dc7932927a8.png)

To view a specific violation, click on the violation to view recent sample payloads that generated the violation. These payloads can then be used to help engineering quickly pinpoint the root cause and release a fix.

If you want to analyze or build custom alerts based on inbound violations, you can [enable violation forwarding](/docs/segment/protocols/validate/forward-violations/).

> \[!WARNING]
>
> Track violations use the `event` field for aggregation, while Page and Screen violations use the `name` field. If these are not properly implemented in your events, violations cannot be aggregated correctly.