Eventstreams and Activator duplicate runs

Hi jajumonville,

Thank you for reaching out to the Fabric support community.

Regarding the query about duplicate runs of Pipelines in Microsoft Fabric, I understand you are facing an issue where the Activator triggers the pipeline twice for the same event. This is causing contention, resulting in one instance failing while the other succeeds. 

Please review the following steps: 

• Please ensure the Event stream is configured correctly to monitor the specific events of interest. Verify whether there are settings or options available to filter events more precisely. 
• Develop a system to assign unique identifiers to each event, preventing multiple activations of the same event. This can be achieved by incorporating metadata or tags into the events. 
• Introduce a debounce mechanism to avoid multiple triggers for the same event in a short period. This can be implemented by adding a delay or cooldown period between triggers. 
• Implement custom logic in the Activators to verify if the event has already been processed before initiating the pipeline. This may involve keeping a record or log of processed events. 

 Please refer Below link: 

Data pipelines storage event triggers in Data Factory (Preview) - Microsoft Fabric | Microsoft Learn 

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.   

Thank you.