web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Getting a 500 code fro...
Power Automate
Unanswered

Getting a 500 code from AppInsights connector for several days

(0) ShareShare
ReportReport
Posted on by

Hi there! 

 

I have a flow that fetches data from AppInsights. However, it has been returning 500 consistently for the past 5 consecutive days. I tried the query directly using AppInsights and successfully fetched the data there. 

 

Can you guys take a look? (Note: I'm an Internal MSFT customer) 

 

Here are a few responses:

{
  "id""6431a4f9-702e-4589-904c-66c51c975704",
  "requestId""dc664498-3d73-43ac-86e6-083a666e8fb5",
  "statusCode"500,
  "errorCode"0,
  "message""An error has occurred. For more information, please check the logs for error ID 6431a4f9-702e-4589-904c-66c51c975704"
}

 

{
  "id""799f6230-d12f-43f1-adb3-33c3cef0645e",
  "requestId""f263ebb5-f02c-412f-9e6c-f8c05d939ded",
  "statusCode"500,
  "errorCode"0,
  "message""An error has occurred. For more information, please check the logs for error ID 799f6230-d12f-43f1-adb3-33c3cef0645e"
}

 

Thanks! 

Categories:
I have the same question (0)
  • v-xida-msft Profile Picture
    on at

    Hi @jasole201503,

     

    Do you use Azure Application Insights connector within your flow?

     

    The 500 error is a temporary or transient failure, click Resubmit to try the flow again. I have made a test on my side and don’t have the issue that you mentioned.

     

    In addition, please consider take a try to re-create a connection to the Azure Application Insights connector and check if the issue is solved.

     

    Best regards,

    Kris

  • jasole201503 Profile Picture
    on at

    The 500 error is not transient. Since I'm an internal customer, an engineer from the AppInsights team did reach out to me off-line and worked with me in resolving this issue. For transparency, to help external customers who might come across this issue, the error was caused by the fact that I was using a beta version of the connector, which has become incompatible, so I ended up recreating the flow, since the Flow webapp prevented me from replacing the connector in the existing flow.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 522 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 364 Moderator

#3
abm abm Profile Picture

abm abm 243 Most Valuable Professional

Last 30 days Overall leaderboard