Solved: Re: I get an error with Todoist Trigger

mirkobersani · ‎09-05-2019

{

"error": {

"code": 410,

"source": "flow-apim-europe-001-westeurope-01.azure-apim.net",

"clientRequestId": "9186d211-c268-4e1a-8d00-03a446becbf5",

"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"

}

v-bacao-msft · ‎09-30-2019

Hi @mirkobersani / @Anonymous / @Arkitekt ,

Please check the new version:

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

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

v-bacao-msft · ‎09-05-2019

Hi @mirkobersani ,

Thank you for your feedback. I did the test here and I did meet the same problem.

Just yesterday I was still using this connector-related action for testing, but now obviously this feature may be temporarily unavailable.

The new version of the API has been released for the service involved in the connector, and it seems that the previous version has been deprecated, so this API endpoint is no longer available.

MS Flow will respond to this situation to ensure that the connector-related functionality is working properly.

Thank you for your support again.

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Arkitekt · ‎09-06-2019

How long should we expect this to be broken? I'm in the same boat and rely on this connector to update my tasks across several visility systems and doing it manually is not something I want to have to deal with for too long. If it's going to be broken for months, then I need to look for an alternative solution to accomplishing what I need to do.

v-bacao-msft · ‎09-09-2019

Hi @Arkitekt / @mirkobersani ,

We have reported this issue.

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

mirkobersani · ‎09-09-2019

Thanks for the update.

Now, what is the process? There is an estimation about the resolution date?

Anonymous · ‎09-10-2019

Hi,

Experiencing this issue too, very frustrating.

Contact Todoist and they said it's "Flow" issue and won't help.

Any idea when this will be rectified by Flow?

Thank you.

v-bacao-msft · ‎09-11-2019

Hi @mirkobersani ,

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

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Anonymous · ‎09-19-2019

Do we still look to be on schedule for the 25th? I know I can’t be the only person having issues with this broke.

mirkobersani · ‎09-20-2019

I'm having huge issues with this broken. I'm waiting for the fix and hope it'll be 25th.

mirkobersani · ‎09-25-2019

Hello @v-bacao-msft ,

are there any updates about the matter?

Thanks

Mirko

Anonymous · ‎09-25-2019

Okay, I am checking in on this matter as well. I need to see if this has traction at all as I going to have to move over to Zapier if MS Flow can't get this working.

@v-bacao-msft

v-bacao-msft · ‎09-26-2019

Hi All,

The new version of the connector has been developed and is currently in the Preview phase. Some regions have not yet been deployed, so stay tuned.

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

mirkobersani · ‎09-30-2019

Hi @v-bacao-msft ,

thank you for the update.

I'm waiting for this fix since the start of this thread.

For me, it's very difficult to work without this integration.

I'm in Italy, when does it's planned the deploy in my region?

Mirko

v-bacao-msft · ‎09-30-2019

Hi @mirkobersani / @Anonymous / @Arkitekt ,

Please check the new version:

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

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

mirkobersani · ‎10-01-2019

Ok, It works fine to me.

mirkobersani · ‎11-05-2019

hi @v-bacao-msft,

I discovered a bug using the v2 version of the Todoist connector.

The trigger When a task is completed (V2) (Preview) returns this body

{
"content": "Stretching & Breathing",
"meta_data": null,
"user_id": 5123746,
"task_id": 3463747610,
"project_id": "2215864327",
"completed_date": "2019-11-05T08:35:51Z",
"id": "3356452419"
}

Consuming the result in a next step, into the property itemTaskId, I got the value of id, and not task_id.

I don't know what is id, but I need the task id.

The current error message is:

Could you please fix it?

v-bacao-msft · ‎11-05-2019

Hi @mirkobersani ,

You could get task id via expression:

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

mirkobersani · ‎11-06-2019

Ok, this way works.

Maybe, I would fix the out of the box property "task_id" for the users who don't know the difference.

dkeiller · ‎02-08-2023

Hi,

I am getting the same 410 error from a Todoist action.

{
"error": {
"code": 410,
"source": "india-001.azure-apim.net",
"clientRequestId": "eeec4ecf-2a98-4c9d-9eba-f9d32f3faca4",
"message": "The response is not in a JSON format.",
"innerError": "Gone"
}
}