Azure-docs: This debugging ability does not help at development time during setting up triggers and linked connection services.

[samiarahman]

I am currently trying to add a blob trigger and it does not start and comes back with internal server error. There is no way to debug if the configuration itself is having issues. Also it's taking me more than 3 days of working to debug and try to resolve any issues without appropriate error messages, without any unit test capability and without any overall pipeline test ability where I mock a blob trigger or simulate time. What is Azure data factory best practice recommendation?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 5abe92e0-af6a-4def-ca04-cec316529945
• Version Independent ID: 96e2ab4c-46cd-e996-fb11-1423b2325928
• Content: Iterative development and debugging in Azure Data Factory
• Content Source: articles/data-factory/iterative-development-debugging.md
• Service: data-factory
• GitHub Login: @djpmsft
• Microsoft Alias: daperlov

[samiarahman]

The specific error I see is "Trigger Activation error" "Failed to get subscription status on storage events for event trigger: trigger_name"

[KranthiPakala-MSFT]

@samiarahman Thank you for reaching out and bringing this to our notice. At this time we are reviewing the feedback and will provide an update as appropriate

[tcz001]

It turns out the missing part is the trigger is trying to create a event subscription on ADLS gen2 Storage account, which failed on the Storage account side, There seems in some regions Storage Accounts are missing this EventGrid Subscription feature, so you should document this requirements when we use event trigger function.

[djpmsft]

@tcz001 Events are only available in West Central US and West US 2 at this time. You are right this is not properly documented or clear in the UX. Luckily, the ADLS team is currently rolling out the feature in all regions and this issue should no longer be apparent by the end of the week!

please-close

[tianlai]

@djpmsft I think it would be a better practice to close this ticket with specific information when ADLS team rolls out the feature. "Coming soon" doesn't really mean it's resolved. I would be surprised this is how Microsoft tracks things.

[sparianer]

@djpmsft I just can confirm the statement of @tianlai .
It took me quite a time to find out, that this issue is not a problem of my code/settings, but an Azure problem.
There is no hint or message at all when you configure a trigger that way. sigh

BTW: The posting announcing the roll-out is more than two weeks ago and the error is still occurring in region Europe West.
How is the current state/planning?

[djpmsft]

As of two weeks ago, ADLS gen 2 had events enabled in all regions. If you are running into issues with events, please reach out to the ADLS team.

@sparianer what is the error you are getting? There is a chance it may be a different issue.

[sparianer]

It's the same error message as mentioned above:
"Failed to get subscription status on storage events for event trigger: "

In _View detail_ there is only a common message "InternalServerError executing request"

The trigger looks the following way: