Unanswered

Error: Http request failed: the content was not a valid JSON. Error while parsing JSON: 'Unexpected character encountered while parsing value: R. Path '', line 0, position 0.'

(2) Share

Report

Posted on by E_S

I am trying to write a flow and I get this error:

Http request failed: the content was not a valid JSON. Error while parsing JSON: 'Unexpected character encountered while parsing value: R. Path '', line 0, position 0.'

The flow it's really simple, variables and an execute query.

I am trying to get texts from power app and use them to modify a string variable in power automate. Then I use the modified string variable as a query.

I start with a trigger from power apps and I specify what I want to save as a variable and use in power automate:

Then I have a variable to save my query as a string and I use the previous variable to modify it (I find it in the required fields).

Here it seems that everything works, but I do not understand what is "Impostavariabile_valore".

The error appears in the last step, when I try to execute the query

Can you give me some advice?

Categories:

Building flows

I have the same question (0)

All responses (54)

Answers (1)

DEV_SCASSIANO 2 on at

Like (0)

Report

**bleep**, I occur the same error!

Was this reply helpful? Yes No
Verified answer

David Pezzoli 230 on at

Like (0)

Report

I think it is a generic flow error:
Try to paste in the correct format the query directly into the action: "Esegui una query SQL"
In this way, you might get the exact new error of your query.
Here is another solution using Try/Catch in order to detect a specific error:

https://powerusers.microsoft.com/t5/General-Power-Automate/Error-while-parsing-JSON-Unexpected-character-encountered-while/td-p/1404831

Was this reply helpful? Yes No
David Pezzoli 230 on at

Like (1)

Report

Try to using correct OData format, as example for SQL Sever Get Rows filter query:
ERROR: colRowId eq QR000001
OK: colRowId eq 'QR00001'
the second will be accepted because you explain with quotes '' it is a string

Was this reply helpful? Yes No
jeffMazUr 2 on at

Like (0)

Report

Friends,
In my case, it worked putting the name of the O'DATA Filter column between quotation marks - because it has a graphic accent (pt-br) and spaces - simple as well as the value you want to compare.
Ex.:
'N_x00fa_merodes_x00e9_rie' eq '0ARYBJEM30001W'
Remembering: You must inform the column name as it appears when using the field in an expression.

Was this reply helpful? Yes No
binki-dcx 70 on at

Like (1)

Report

I got this same exact error on a flow which normally works fine. If I understand correctly, the remote endpoint is claiming that the input the flow provided is malformed. There is no way for us to debug this—it requires Microsoft to look into it.

It could be that some logging in the flow stuff gets written to the request. Or the flow request logic is written in a way which is not threadsafe so that an HTTP header shows up in the middle of the request body.

Here’s my error in a request to Outlook’s Reply to Email (V3):

Http request failed: the content was not a valid JSON. Error while parsing JSON: 'Unexpected character encountered while parsing value: R. Path '', line 0, position 0.'

Was this reply helpful? Yes No
nerfherder 128 on at

Like (2)

Report

@binki-dcx I've gotten that exact error 4 separate times today, on 4 separate flows, all on the "Send an email from a shared mailbox (V2)" action part of them.

All of them went through on a resubmit, so a good use case for a custom workflow failure monitoring solution and hopefully something that knocks it off soon.

Was this reply helpful? Yes No
David Pezzoli 230 on at

Like (0)

Report

My advice is take glance the correct syntax of: the expressions, OData query or SQL query. Sometimes it's necessary add the quotes '....' and the blank spaces to the right place. So, look for similar examples on the Web that use the same steps. Check carefully the exact syntax of the steps used in the Web examples. Make sure the Web examples are recent blogs (with most PA updated version).

Was this reply helpful? Yes No
binki-dcx 70 on at

Like (3)

Report

@nerfherderInteresting. Sounds like that particular service was broken for a while then.

@David_PezzoliPlease understand that this error comes up when Power Automate itself is having a temporary error or incorrectly handling transient errors from connected services. It has no relation to the correctness of our flows or expressions in our data. Did you read the thread or ever experience this error yourself?

Was this reply helpful? Yes No
David Pezzoli 230 on at

Like (1)

Report

Maybe it could be an error due to a recent update in Power Automate of the version of the action? From my experience, when a new version of the action is released, sometimes the syntax also changes ....however, I agree with you that this is too general a mistake and sometimes temporary!

Was this reply helpful? Yes No
nerfherder 128 on at

Like (2)

Report

@binki-dcx Never had this error before the other day, just had it again on a 5th flow. Resubmitting without changing source code results in successful run (error cannot be replicated?).

@David_Pezzolithere are not any new actions, expressions, or queries of the SQL or ODATA variety here. just plain dynamic content from one action to the next.

whats the trick to getting someone from microsoft to see/respond to this thread?

Was this reply helpful? Yes No