Hi, I am also facing a similar issue in ITSI after enabling Bidirectional Ticketing. Once the ServiceNow ticket is created and the bidirectional event is generated, subsequent events with the same criteria are getting ignored and are no longer being added to the episode. It looks like the episode grouping behavior changes after the bidirectional event is introduced, possibly due to how the Rules Engine or aggregation policy evaluates incoming events. In my case, only the bidirectional ticketing events continue to be processed, while normal “Service Monitoring - Entity Degraded” events are being filtered out. Has anyone confirmed whether this is expected behavior or if there is a recommended configuration to prevent bidirectional events from affecting episode event ingestion? Any guidance on adjusting split-by fields or filtering logic in NEAP would be appreciated. ... View more