Event Trigger is not firing Synapse pipeline

Question

I have created an Event Trigger in Synapse to trigger pipeline based on file arrival in a certain container.

The trigger creation created the event subscription in my storage account and whenever I upload a file, I can see the events in the event subscription part.

However, the pipeline I have attached the trigger to does not trigger on the event.

My Synapse instance has:

• Contributor
• Storage Blob Data Contributor
• Storage Account Contributor permissions on the storage account. I have also added Azure Data Factory Enterprise Application as Contributor in storage account.

Storage account is behind a network firewall and has allowed MS trusted services to pass through.

Can someone please guide on what I am missing with the Event trigger?

Answer 1

Hi Shaan Shastri,

Thanks for reaching out to Microsoft Q&A.

To troubleshoot why your Synapse Event Trigger isn’t firing, even though events are arriving in the subscription, consider the following points:

1. Check Trigger Configuration:

• Ensure the Event Trigger is correctly configured to monitor the specific container path and file type (e.g., .csv, .json) in the Blob Path Begins With and Blob Path Ends With fields. Any mismatch can cause it not to trigger.

1. Verify Network and Firewall Settings:

• Since the storage account is behind a firewall, confirm that both Azure Synapse and Data Factory IPs are allowed, in addition to enabling Microsoft Trusted Services access. This can sometimes be an issue if Synapse IPs are accidentally missed.

1. Confirm Pipeline Triggering:

• Go to Monitor > Triggers in Synapse Studio and check if the Event Trigger is active. If it shows as inactive, activate it.
• In the Monitor > Pipeline Runs, look for any errors or indications of failed attempts to trigger the pipeline, as this could signal configuration or permission issues.

1. Permissions on the Event Grid Subscription:

• Although permissions look correct, try explicitly granting the EventGrid Event Subscription Contributor role to the Azure Synapse/ADF’s managed identity on the storage account. This role specifically manages event subscriptions.

1. Retry Policy and Event Expiration:

• Confirm that the event trigger doesn’t have custom retry or expiration settings that could be causing it to skip events if they don’t meet certain criteria in time. This setting is often under the event trigger properties.

1. Check for Dependencies on Synapse Link:

• Occasionally, delays or conflicts occur if Synapse Link or other integration components are in use on the storage account. Temporarily disable these, if possible, to rule out interference.

After trying these, if the issue persists, checking logs under Azure Monitor or Log Analytics for any event delivery or permission-related errors can provide more insights.

Please feel free to click the 'Upvote' (Thumbs-up) button and 'Accept as Answer'. This helps the community by allowing others with similar queries to easily find the solution.