Based on the research, this issue could be happening for a few potential reasons. To help you better, I need some additional information: 1. What type of event trigger are you using? (e.g., Deployment Event Trigger, Schedule Event Trigger, etc.) 2. Could you share the trigger configuration you're currently using? However, here are some common causes and potential solutions for multiple triggering: 1. Trigger Configuration Issue - Make sure your trigger criteria are specific enough - Check if you have any overlapping trigger conditions - Verify that the 'expect' and 'match' parameters are correctly set for your use case 2. Event Deduplication - Events might be getting duplicated at the source - Consider adding a unique identifier to your events to prevent multiple processing 3. Trigger Timing - The ~30 minute delay between runs suggests there might be a timing-related configuration that's causing retries or multiple activations - Check if you have any retry policies or "within" periods configured To properly diagnose and fix this, could you please share: 1. The trigger configuration you're using 2. The type of event that's triggering the flow 3. Whether this behavior started recently or has always been present This will help me provide a more specific solution to your issue.