Answered

Error while parsing JSON: 'Unexpected character encountered while parsing value: A. Path '', line 0, position 0.'

(1) Share

Report

Posted on by Community Power Pla...

Hi there,

I have a flow created that uses SQL connector to connect to a database view and pulls records from there and adds few records to excel.

The flow is scheduled to run once a day and is generally working fine. But at regular intervals failing with the below error. Without changing anything in the flow the flow again runs successfully on the next day or even if i resubmit the flow on the same day.

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

Need immediate help on this.

Please suggest.

Thanks

Categories:

General topics

I have the same question (0)

All responses (10)

Answers (2)

jinivthakkar 4,187 on at

Like (0)

Report

@Anonymous please share for which action you are getting the error, also please can you share a sample value for which you are getting the error

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi,

Connector used in SQL.
Pulling data from a SQL DB View and Filter clause is used to filter the data between a range of dates.
The filter and the data pulled from view seems to work fine as immediately if i resubmit it gets successful.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Anyone able to guide as why this error occurs intermittently?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi, Please find below the screenshot where i get this error and also the flow is not failing always. Only some of them fail.

The filter condition used in the query is
WO_x0020_Date ge 2022-01-01 AND WO_x0020_Date le 2022-01-31

The same flow when submitted again runs successful.
Flow runs are like below, suddenly in the middle it fails one or 2 days.. then successful again.

Also because the error says unexpected character in Line 0 Position 0, I'm not able to track or spot the issue yet.

Any help would be very useful.

Thanks

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

@jinivthakkar - Thank you, as per your suggestion in another message implementing try,catch,finally in my flow to handle the scenario. I believe that would be the ideal solution to manage the unpredictable error as above.

Was this reply helpful? Yes No
Verified answer

jinivthakkar 4,187 on at

Like (0)

Report

@Anonymous please accept as solution and close the thread, cheers !

Was this reply helpful? Yes No
Verified answer

Community Power Pla... on at

Like (1)

Report

As posted by @jinivthakkar ,

yesterday
"Recently someone on the forum was getting the same error because the connector was blocked on the environment, by any chance do you have another environment, if yes please can you move your flow and try running the same ?
Also implementing a try catch finally would help to pinpoint the error or even help you in overcoming this
https://www.youtube.com/watch?v=a6rGbJXsH1U&t=2s
Please check out the video, hope that helps."

Was this reply helpful? Yes No
y2kardell 147 on at

Like (0)

Report

Just received this message from Microsoft as the issue has been resolved:
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.&#39
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.

Was this reply helpful? Yes No
fw100 6 on at

Like (2)

Report

I'm really getting tired of Microsoft's poor programming and lack of quality control.

Was this reply helpful? Yes No
DuneZerna 2 on at

Like (0)

Report

So, whats the solution?

Was this reply helpful? Yes No