cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Mattw112IG
Impactful Individual
Impactful Individual

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.'

gettting this today in my send an email?

 

I've looked at the email and cant figure out what character it may be talking about?

 

Saw a couple other people getting this too.  Is this an issue with the action or real error?

 

I'm just doing simple html email.  I've run the html through a validator and it says it is fine.  I know that is different from json though.

 

Terry

28 REPLIES 28
amberschiffer
Frequent Visitor

@jutrust How do you do that? Did you open a ticket with them directly? Or go through your company's IT team?

 

I'm an admin and so went through https://admin.powerplatform.microsoft.com/

y2kardell
Helper III
Helper III

I am an admin and submitted it to them from the admin center. They have responded stating that they are aware of the issue and are working to get it resolved and wanted to setup a call with me once its resolved to test it - although the problem is intermittent something which I have stated to them. So I advised them to inform me when they have resolved the issue and if I come across it again I will reach out to them for a followup.

Dharam2
Regular Visitor

Dharam2_0-1668073293512.png

 

I am facing same error with below connector:

Send an email (V2)

Office 365 Outlook

Please help me out. This issue is occurring frequently.

Your To: shows an absolute nonsense string. It has to be an email address.

 

Please check the value of To: before passing it into the Send an Email action. Please send the picture from the edit mode so we can see how you compose the email.

Interesting.  I've certainly had the wrong data get pulled into the To: field before... obviously causing failure.

 

But when that is the culprit, I get this error message:

The 'inputs.parameters' of workflow operation 'Send_an_email_from_a_shared_mailbox_(V2)' of type 'OpenApiConnection' is not valid. Error details: Input parameter 'emailMessage/To' is required to be of type 'String/email'. The runtime value '"9/28/1957"' to be converted doesn't have the expected format 'string/email'.

 

Or I get this one:  

One or more recipients are invalid. clientRequestId: 3c26d9ca-fc0b-47d1-84c5-5c2f4a6bb1f4
serviceRequestId: f61888a5-76b4-d8d8-286f-f0a3b4bd5630

 

I don't get the one we've all been getting lately at random

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.'

NicoleHarris
Advocate I
Advocate I

The following comment was posted on the Facebook post I created for this issue in the Power Apps & Power Automate group:

Kardell Ferguson Jr.
The problem has been resolved: We have completed all our findings regarding this issue with the help of our product team,

Issue - Send an Email (V2) action fails with the following error message. 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.'

Findings - Our logs indicated that the same role instance LargeDedicatedWebWorkerRole_IN_26 failed to load the certificate around 2022-11-02 at 22:06:15. Typically, this means, that the role instance had trouble getting at its certificate store. Thus, our product team rebooted the worker on 11/09 and that mitigated the issue.

Outcome - Dev team has mitigated the issue and is working on improving worker health checks in order to ensure the issue does not reoccur.

Root Cause - A bad worker was intermittently failing in an internal service that handles access tokens, causing unexpected errors to occur for a small subset of users.

Cool. Thanks!  I just requested to join the group 🙂

 

Was this posting from someone at Microsoft?  Because this issue is happening to a very wide range of people across many businesses. 

Based on the detailed explanation I believe it was someone from Microsoft who posted this update.

Helpful resources

Announcements
Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Top Solution Authors
Users online (3,007)