Issue

When using Destination Filters, you may find that events are filtered out and fail to reach your intended destination, even though the event matches the criteria for one of the filters. 

Product

Twilio Segment

Environment

Segment Console

Cause

This behavior occurs when multiple Send Only destination filters are actively enabled for the same destination instance. When more than one Send Only filter is active, they compete with each other and it creates a logic that is impossible to sequentially satisfy. Because an outbound event cannot simultaneously satisfy multiple separate Send Only routing criteria, the filters conflict and cause all matching events to be dropped instead of delivered.

Resolution

To resolve this issue, you must ensure that only one Send Only filter is active for the destination instance at any given time.

1. Navigate to your Segment workspace.

2. Go to Destinations and select the specific destination that is missing events.

3. Click on the Filters tab to view your active configurations.

4. Review the active destination filters and identify the conflicting Send Only filters.

5. Determine which filter contains the correct criteria for your implementation.

6. Disable or delete the secondary filter so that only a single Send Only filter remains active.

7. Produce a new event or trigger a test event to confirm that delivery to the destination has resumed as expected.

Additional Information

If you require complex or multi-conditional filtering logic for a single destination, consider combining your criteria into a single destination filter utilizing Filter Query Language (FQL) to handle more specific logic that the UI is able to create.