Logic app not triggering when a blob is added or updated in one tenant, but works in another.

Pål Bøckmann 0 Reputation points
2024-09-03T07:06:59.6933333+00:00

I have created a logic app in Azure that should trigger when a blob is added to a container.

bilde

And here are the storage account containers:
bilde

The logic app and the storage account are in the same resource group.

I have re-created the connection from the logic app to the storage account several times to confirm it's correct, and I have also given the logic app contributor rights to the storage account (although I don't think that should be necessary). When I add a new blob to the sysvak container, the logic app does not trigger at all. It does not matter which directory inside the container I place the blob in. No runs appear in the run history so there are no logs to examine.

I have created the exact same setup in another Azure tenant, literally copied the code word for word with the exact same containers, and there it works perfectly. That is however not the tenant I need the logic app in, so I need to get it working in the first tenant. What could be wrong here?

Possibly related, I have also been having some other issues with this logic app. I am sometimes met with this error message when trying to view the list of workflows:

bilde

And this error message when trying to view the workflow designer:

bilde

It's seemingly random when the error messages appear and when it loads fine.

In the logic app that is not working there is a bunch of messages in the app insights log saying that the listener has stopped
bilde

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,087 questions
0 comments No comments
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.