Data 360 Triggered Flow Behaviour

When setting up a Data 360 Triggered Flow to publish a segment upon the addition of new records to a DMO, you might notice that the segment is published multiple times within a single hour. This is because the flow is functioning as designed, responding to each individual record that matches the criteria set in the DataAction.

In scenarios where no filter criteria are specified in the start node of the flow, the DataAction will trigger the flow for every new record in the DMO. While the DataStream itself may update hourly, this does not limit the DataAction to a single event per hour. Instead, the DataAction will issue multiple events for records matching its criteria, causing the flow to run multiple instances, or "interviews," for each event.

The errors observed, such as overlapping or concurrent segment publishes, occur when a segment is attempting a publish while a previous publish operation is still in progress.