Todoist: the response is not in a JSON format

[mark2890]

Hi community,

I have issues connecting my Todoist to any workflow in Flow. When I try to enter the Project ID, it tells me the error message "Values could not be retrieved (translated from German). The response is not in a JSON format." 

It failed when I tried to use an MS Planner task as a trigger for a Todoist task. However, I have the same problem with any connection to Todoist. Seems it cannot establish the connection with Todoist.

Has anyone had the same problem with Todoist before? Can the MS team help please?

Thanks a lot!

Mark

[v-bacao-msft]

Hi @mark2890 ,

We have reported this issue, please check this similar thread:

https://powerusers.microsoft.com/t5/I-Found-A-Bug/Todoist-APIs-are-failing/td-p/356565

Best Regards,

[Earp]

I had the same problem. All my Todoist flows started failing last Thursday. I reached out to Todoist and receivied the following response:

Thanks for contacting us about this.

We've spoken to our developers about this It looks like the issue lies with MS Flow. We recently deprecated v7 of our API and moved to v8 (REST API). We have previously informed MS Flow about this and asked them to make the necessary changes. Since it's a 3rd party integration, we're unable to troubleshoot and fix it on our end as it's up to Microsoft. Sorry about that!

Could you please reach out to MS Flow's support so they can take a look? Many thanks!

[pi24]

I just got this message from todoist. Can someone pass this on to Microsoft flow support?

Hi Leigh,

Thank you very much for reporting this. I'm terribly sorry for our delayed response - we've unfortunately had a large backlog in support 😓I'll be here to assist you from now on 👍

We've spoken to our developers about issue. It looks like the issue lies with MS Flow. We recently deprecated v7 of our API and moved to v8 (REST API).

We had previously informed MS Flow about this and asked them to make the necessary changes. Since it's a 3rd party integration, we're unable to troubleshoot and fix it on our end. Sorry about that! It looks like MS Flow would need to resolve this.

Could you please reach out to MS Flow's support so they can take a look? Many thanks 😊

Best Regards,
Malin

[v-bacao-msft]

Hi All,

The new version is under development right now. 
Approximate ETA is September, 25th

Best Regards,

[v-bacao-msft · Accepted solution]

Hi @mark2890 / @pi24 / @Earp ,

Please check the new version:

https://docs.microsoft.com/en-us/connectors/todoist/#onitemcompletedv2

Best Regards,

[tubu]

three years on and the problem persists. I have tried the Todoist Connector v2 and v3. Is there anyone else facing this issue?

[Portugees]

Yes, currently facing the issue as well. None of my Todoist related flows seem to work anymore. Also I cannot retrieve my list of projects from within PowerAutomate. I have recreated connectors and a couple of flows to no avail.

[jamie_lav]

I'm glad I'm not the only one suffering this issue. I have two separate flows that both send data from Office 365 Outlook to Todoist, however as of December 5th neither have worked and are throwing up the above error.

[shimon001]

Hi, I am having the same issue. I found and advice to use v2 (or v3) version of the Create Task action but this fails as well with this output: 

{
    "statusCode": 410,
    "headers": {
        "X-Cache": "Error from cloudfront",
        "X-Amz-Cf-Pop": "ORD56-P1",
        "X-Amz-Cf-Id": "AMQ-uCpsQt9iPo-VdjC_kb-4YWH4sMa2QISuzT4M4O6WU52wangB9w==",
        "Strict-Transport-Security": "max-age=31536000; includeSubDomains; preload",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "false",
        "x-ms-apihub-obo": "false",
        "Date": "Tue, 03 Jan 2023 13:33:44 GMT",
        "Via": "1.1 9832e15ad117dafc81b031983cbde91e.cloudfront.net (CloudFront)",
        "Content-Length": "257",
        "Content-Type": "application/json"
    },
    "body": {
        "error": {
            "code": 410,
            "source": "flow-apim-msmanaged-na-centralus-01.azure-apim.net",
            "clientRequestId": "3102326c-1988-4b64-a4ac-b93782d4b85c",
            "message": "The response is not in a JSON format.",
            "innerError": "Gone"
        }
    }
}

It would be great if somebody from PowerAutomate support could have a look at this as this is an integration managed by Microsoft team. 

[kago76]

Hi,
we have the same error since December 2022. 
Create Task v2 and CreateTask v3 failed with error message "The response is not in a JSON format."
But: It is in Json format. 

Please repair the connector.

Greetings,
Kai

[Tman]

This should no longer be an accepted solution. JSON error seems to be common among users...

[xoec]

Adding to the chorus of people having the same problem.