Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
logic app - trigger error - InternalServerError
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 48%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Alfred McNair
1
Reputation point
When attempting to use the SQL "Item created" trigger in a logic app, my activity log shows several failed triggers.
When I view the History, I see the code: "InternalServerError"
The inputs link appears to be functional
The outputs link shows the data that I expected in the body (see image below)
However, the trigger Status is always failed, the Fired column is blank and there is no run history to trace back to the point of failure.
Azure Logic Apps
{count} votes
-
Kamlesh Kumar 3,871 Reputation points2022-06-02T14:55:14.47+00:00 Hi @Alfred McNair ,
Thank you for asking this question on the Microsoft Q&A Platform.
"InternalServerError" is generic error which means that the service was not able to process the request due to some issues. Could you please confirm if database connectivity established and you are able to connect SQL?
Also, if possible to share the flow screenshot to understand your design of workflow.
Regards,
Kamlesh Kumar
BizTalk TechiePlease don't forget to click on
or upvote 
button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is How Want a reminder to come back and check responses? Here is how to subscribe to a Notification
If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators
-
MayankBargali-MSFT 70,981 Reputation points Moderator2022-06-03T10:00:37.087+00:00 @Alfred McNair Thanks for reaching out. Can you please confirm if you see the error in the "Trigger history" or "Runs History" of you workflow? If in case it is the trigger history then the worflow will be triggered as per your configured
How often do you want to check for items?property. It looks like your when an item is created (v2) action item is not configured correctly or the SQL connector is not able to estanblished the connection with the SQL database. Can you please navigate to your resource group --> Your SQL connector resource --> Verify the Status if it shows asConnected?
If it is not connected, then please verify if there is any firewall configured at your SQL end that is blocking the connection.In case if you are still facing the issue then please share more details what authethication you are using in your trigger action to connect to your SQL resource.
Sign in to comment
Sign in to answer