cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
obrica
New Member

Template flow "Create Todoist Tasks for Flagged Office 365 emails" failing due to JSON error

I'm trying to use and implement the public template "Create Todoist Tasks for Flagged Office 365 emails." Absent any modification, the flow has issues before even running it; attempting to select a Todoist Project ID shows the following error:

"There's a problem The response is not in a JSON format. More diagnostic information: x-ms-client-request-id is '833AFBC6-C4F7-4BEB-880D-C6F43DFE60D7'."

obrica_0-1661452756680.png


Predictably, the same error occurs if you try to run the flow:

obrica_1-1661452794556.png


Is there a way to solve this by modifying the template? I've read other posts on this forum about JSON errors for other flows and integrations (with various solutions), but not for this specific one.

1 ACCEPTED SOLUTION

Accepted Solutions
Expiscornovus
Super User
Super User

Hi @obrica,

 

It looks like that template is using the deprecated Create a Task action:

https://docs.microsoft.com/en-gb/connectors/todoist/#create-a-task-[deprecated]

 

When building a new flow that action is not even selectable in the interface. My guess is this old action is causing this error.

 

I would just start from scratch, to be honest. The template only contains two actions.

 

With the Create a Task (v2) the setup would be like below.

 

flaggedemail.png



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #PowerVirtualAgents content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


View solution in original post

5 REPLIES 5
Expiscornovus
Super User
Super User

Hi @obrica,

 

It looks like that template is using the deprecated Create a Task action:

https://docs.microsoft.com/en-gb/connectors/todoist/#create-a-task-[deprecated]

 

When building a new flow that action is not even selectable in the interface. My guess is this old action is causing this error.

 

I would just start from scratch, to be honest. The template only contains two actions.

 

With the Create a Task (v2) the setup would be like below.

 

flaggedemail.png



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #PowerVirtualAgents content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


obrica
New Member

Great, thank you!

Hi @Expiscornovus , it seems that even the v2 Create Task action is now deprecated and returns this output: 

 

 

{
    "statusCode": 410,
    "headers": {
        "Transfer-Encoding": "chunked",
        "Vary": "Accept-Encoding",
        "Referrer-Policy": "strict-origin-when-cross-origin",
        "Strict-Transport-Security": "max-age=31536000; includeSubDomains; preload",
        "X-Content-Type-Options": "nosniff",
        "X-Cache": "Error from cloudfront",
        "X-Amz-Cf-Pop": "ORD56-P1",
        "X-Amz-Cf-Id": "NnElwVfgnCXNtZT0K6NSlk0vhyyS2FK2QccmPWyEDLtW8APUMJa23w==",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "true",
        "x-ms-apihub-obo": "false",
        "Date": "Tue, 03 Jan 2023 10:52:14 GMT",
        "Via": "1.1 9d71affbaf22baf23eab459f3d2ee77a.cloudfront.net (CloudFront)",
        "Content-Type": "application/json",
        "Content-Length": "663"
    },
    "body": {
        "error": {
            "code": 410,
            "source": "flow-apim-msmanaged-na-centralus-01.azure-apim.net",
            "clientRequestId": "ad5903fc-c1d2-4ddc-9626-189a550d071a",
            "message": "The response is not in a JSON format.",
            "innerError": "This endpoint is deprecated.\n\nIf you're reading this on a browser, there's a good chance you can change\nthe v8 part on the URL to v9 and get away with it. ;)\n\nIf you're using the API directly, please update your use case to rely\non the new API endpoints, available under /sync/v9/ or /rest/v2/ prefixes.\n\nFor more details, please see documentation at\nhttps://developer.todoist.com/guides/#our-apis\n\n"
        }
    }
}

 

I've also tried the Create Task (v3) preview action but it fails as well. Can you please advise how to fix this? 

Expiscornovus
Super User
Super User

Hi @shimon001,

 

It looks like the the v2 action uses v8 version of the Todoist REST API. However, that version has been deprecated by Todoist:

https://developer.todoist.com/sync/v8/#overview

 

It looks like Microsoft is the publisher of this connector:

https://learn.microsoft.com/en-us/connectors/todoist/

 

If you get the same error in the v3 action as well I would advise to contact Power Automate support for this:

https://powerautomate.microsoft.com/en-us/support/

 



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #PowerVirtualAgents content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


shimon001
New Member

Hi @Expiscornovus, thanks for your reply! I was trying to get to some support directly from Power Automate support team but I can't seem to find any form where I could submit my issue even though I am logged through our company Office 365 account. The support site itself seems to be broken because when I click on "Contact support" support it only shows the information about "Community" vs. "Assisted" support without any option to submit an issue 😞 

Helpful resources

Announcements
Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Community Calls Conversations

Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Users online (1,398)