Unanswered

400-error & BadRequest

(0) Share

Report

Posted on by Victoria_mm38

The flow build and used for more than 2 year without any error, these issues happen yesterday and I have searching all over the places for a solution. Please help:

Output - Body:

{

"error": {

"code": 400,

"source": "asia-001.azure-apim.net",

"clientRequestId": "04f7370e-a6b3-4150-bc63-2cd6058b3162",

"message": "The response is not in a JSON format.",

"innerError": "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01//EN\"\"http://www.w3.org/TR/html4/strict.dtd\">\r\n<HTML><HEAD><TITLE>Bad Request</TITLE>\r\n<META HTTP-EQUIV=\"Content-Type\" Content=\"text/html; charset=us-ascii\"></HEAD>\r\n<BODY><h2>Bad Request - Request Too Long</h2>\r\n<hr><p>HTTP Error 400. The size of the request headers is too long.</p>\r\n</BODY></HTML>\r\n"

}

Outout - Header:

{

"Timing-Allow-Origin": "*",

"x-ms-apihub-cached-response": "true",

"x-ms-apihub-obo": "false",

"Date": "Thu, 08 Dec 2022 09:28:07 GMT",

"Content-Length": "592",

"Content-Type": "application/json"

}

All responses (3)

Answers (0)

Expiscornovus 31,635 Most Valuable Professional on at

Like (1)

Report

Re: 400-error & BadRequest

Hi @Victoriamm38,

Yes, that looks like a pretty simple setup. The error suggests something is wrong with the When a file is created action. Couple of follow-up questions.

Have you checked the connection, is it still ok? Which folder did you use in the trigger action. The root?

Have you configured a trigger condition in the settings of the trigger action? If so, can you share that expression?
Victoria_mm38 3 on at

Like (0)

Report

Re: 400-error & BadRequest

Hi @Expiscornovus ,

My flows is very simple:

It shown the error message like following:

Since it happen my flows never triggered and run whenever a file is uploaded into the onedrive folder.

Please help.

Thank you!
Expiscornovus 31,635 Most Valuable Professional on at

Like (0)

Report

Re: 400-error & BadRequest

Hi @Victoriamm38,

Can you share a bit more information about your setup? For example, which action is showing the error and what connector are you using?

Are you by any chance using a ToDoIst action/connector in your setup?

Recently I saw a similar thread about that on these forums:

https://powerusers.microsoft.com/t5/Using-Flows/Todoist-Flows-Failing-JSON-Errors/m-p/1911832