Error Code 500 on MS form Get response details flow not working - Error reading JArray from JsonReader.

[fabiofa]

Hello All,

I'm having trouble with a flow triggered by an MS form submission.

The form is submitted properly and I see responses both in the excel file and on the form itself, but the flow fails at the "get response details" action.

Below is the error message:

Error reading JArray from JsonReader. Path '', line 0, position 0.
at Newtonsoft.Json.Linq.JArray.Load(JsonReader reader, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JArray.Parse(String json, JsonLoadSettings settings)

{
    "statusCode": 500,
    "headers": {
        "Access-Control-Allow-Methods": "GET, PUT, PATCH, DELETE, POST",
        "Access-Control-Allow-Origin": "*",
        "Access-Control-Max-Age": "3600",
        "Access-Control-Expose-Headers": "*",
        "Date": "Mon, 16 Jan 2023 23:39:20 GMT",
        "Content-Length": "504",
        "Content-Type": "application/json"
    },
    "body": {
        "error": {
            "code": 500,
            "message": "Error reading JArray from JsonReader. Path '', line 0, position 0.\r\n   at Newtonsoft.Json.Linq.JArray.Load(JsonReader reader, JsonLoadSettings settings)\r\n   at Newtonsoft.Json.Linq.JArray.Parse(String json, JsonLoadSettings settings)",
            "source": "flow-apim-msmanaged-na-eastus2-01.azure-apim.net",
            "path": "choose[2]\\when[1]\\choose[1]\\when[1]",
            "policyId": "",
            "clientRequestId": "bd8f79da-a3ef-477c-97e9-4d5a7595e53f"
        }
    }
}

Does anyone know why this is happening and/ or has a workaround to this? Is there any way I can retrieve the submission data from the form without using the "get response details" since I'm having trouble with it?

Thank you!

[MvEikenhorst]

I do have the same issue since yesterday. The user interface in Forms Design seems to have changed a bit. Did something else change so Forms reactions JSON is getting this error in Power Automate getting the Forms reaction connector. Seems to be JSON related.

[MossIT]

Our organization is also experiencing this as of yesterday. All apps that rely on Microsoft Forms are broken due to this issue. 

[MvEikenhorst · Accepted solution]

I did implement a workaround which is working fine. Also discussed with an Microsoft engineer in case more tickets will be created and can be used as a workaround, although this Forms API seems not to documented. It seems like the standard GetFormResonseById connector is failing and is under investigation.

Workaround is using the SharePoint HTTP REST API

And filter by the Response-Id from the Forms trigger. 
Then Parse the JSON body into an array, since you get an array with one item.
And get the details like Responder from the parsed JSON object.

[fabiofa]

Amazing, this works!

Was looking for documentation to connect to the forms API but could not find it so this is definitely a great workaround in cases like these where the connector is down.

Thank you MvEikenhorst!

"GetFormResonseById" seems to be working now, so MS must have fixed it. 

[MossIT]

Main issue appears to be resolved, the workaround shouldn't be needed anymore. 

[tbrt_mrom]

I get this issue too on a flow of mine. However mine is a cloud flow and i dont know how to implement the fix in that context.

[JonathanBoyle]

I've had the same issue as of yesterday as well on a cloud flow.

[tbrt_mrom]

I figured out the solution. It might have something to do with the ID that forms extracts and hands over to the "GetResponseDetails" command. Well some forms just straight up make it fail for no reason. For us the solution was to remake the Form as a new one. Then it suddenly started working and we have no idea why 😕

[tbrt_mrom]

Upddate: I found out that if you dont have any questions in the Forms at all and just text, it will for some reason fail when extracting answer data. Solution is to just make a throwaway question into the empty Forms.

[dwgreen]

Ah! This is exactly what we're doing, and it makes sense a lot for our specific use case (trust me on this one). Good to know this.

[JonathanBoyle]

Ah! This has worked for me as well. I just put in a question asking for the answer to the ultimate question and it worked!