Share via

How to make the Azure Synapse blob trigger work?

Leonardo Kuster Degasperi 0 Reputation points
2023-09-27T17:04:22.88+00:00

I've been struggling for weeks to activate the blob event trigger in Microsoft Azure. The goal is to initiate an Azure Synapse pipeline whenever a blob is created in the path "requests/inputs/{some_blob}.json." I completed the configuration, saved, and published the trigger. However, despite multiple attempts to send files, it hasn't been functioning as expected.

In an attempt to resolve the issue, I also experimented with enabling the EventGrid and EventHub features, but unfortunately, that didn't yield the desired results either.

I'm growing increasingly frustrated with these tests, and I'm beginning to lose hope. Is there anyone who can provide guidance or insights into what might be causing this issue? Your assistance would be greatly appreciated.

User's image

Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,528 questions
Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
4,524 questions
Azure Event Grid
Azure Event Grid
An Azure event routing service designed for high availability, consistent performance, and dynamic scale.
330 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Smaran Thoomu 11,290 Reputation points Microsoft Vendor
    2023-09-28T09:32:18.0366667+00:00

    @Leonardo Kuster Degasperi Thank you for reaching out to us with your query. I'm sorry to hear that you've been struggling to activate the blob event trigger in Microsoft Azure.
    I have tested this in my environment using blob storage account and it works as expected and uploading a file triggered the pipeline.
    User's image

    Before proceeding with the steps can you help us with the error what exactly you're getting?
    Here are some troubleshooting steps that you can follow to identify and resolve the issue:

    1. Ensure that the blob container and the path "requests/inputs/{some_blob}.json" exist in the storage account. You can check this by navigating to the storage account in the Azure portal and checking the "Containers" tab. 
    2. Check the trigger configuration to ensure that it is set up correctly.In the Triggers option you can select the trigger in question and verify that the "Blob path begins with" field is set to "requests/inputs/" and that the "Blob path ends with" field is set to ".json".
    3. Check the logs to see if there are any errors or issues with the trigger.
    4. Azure Blob Storage managed connector actions can read or write files that are 50 MB or smaller. To handle files larger than 50 MB but up to 1024 MB, Blob actions support message chunking.
    5. If the above steps do not resolve, you can try creating a new trigger and testing it with a new blob. This can help determine if the issue is with the trigger configuration or with the blob itself.

    Here are some relevant Azure documentation links that can provide additional information on Azure Synapse Analytics and blob event triggers: 

    Create event-based triggers - Azure Data Factory & Azure Synapse | Microsoft Learn

    Reacting to Azure Blob storage events | Microsoft Learn