Looks like Todoist deprecated their old API endpoint and flows now fail with error:
Is there a fix coming?
{ "error": { "code": 410, "source": "flow-apim-msmanaged-na-northcentralus-01.azure-apim.net", "clientRequestId": "16237bd4-e16e-427c-bd60-bd2a8d349698", "message": "The response is not in a JSON format.", "innerError": "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 3.2 Final//EN\">\n<title>410 Gone</title>\n<h1>Gone</h1>\n<p>This API endpoint is no longer available. Please refer to our documentation to upgrade your client to use the latest API version: https://developer.todoist.com</p>\n" } }
Hi @the-coderok,
Thank you for your feedback. I tested it on my side and got the same problem.
As recently as yesterday, I was testing this connector related operation, but now it's clear that this feature may not be available for a while.
A new version of the API has been released for the services involved in the connector, and it appears that the previous version has been deused, so the API endpoint is no longer available.
MS Flow will respond to this situation to ensure that the functions associated with the connector work properly.
Thanks again for your support.
Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I see, thanks for the information
Is there an ETA for the fix?
Any additional updates on when we can expect this to be fixed? This is crucial to compiling some reporting metrics for my teams. Thanks.
Same issue here, any updates?
How did you let this happen, Microsoft? Super concerning you can't stay on top of API updates - this one was coming for a while. I am not sure I am able to trust flow for my organization anymore.
Can anyone at Microsoft provide a timeline for the fix?
Thank you for your reply @v-litu-msft. I just ran into this same issue. We're all hoping for a fix soon, thank you!!
Fully agree. These are not custom, but standard connectors.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 | |
1 |