Unanswered

Getting a 500 code from AppInsights connector for several days

(0) Share

Report

Posted on by jasole201503 Microsoft Employee

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:

Using flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

v-xida-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
jasole201503 Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

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.

Was this reply helpful? Yes No