Hello, I eventually figured out why this was happening. The events that were being generated by the bidirectional ticketing correlation search were being populated with the "group_id" field. The rules engine would then add this event to the episode. My guess is that when the bidirectional event is "forced" into the episode because of the "group_id" field, the rules no longer work as expected. The bidirectional ticketing correlation search is based on a macro, so I am not sure if that is expected behavior. I can't imagine that it is expected behavior, as it completely messes up event ingestion. Who knows. Anyway, what I did to "fix" it was in the bidirectional ticketing correlation search, add the following line: | fields - group_id Once this line removes the group_id from the bidirectional event, the rules engine no longer adds bidirectional events to the episode, and normal entity degraded events continue to flow into the episode. Hopefully this helps, as it took me forever to figure this out. ... View more