What is the problem?
scenario gets deactivated because of an error 410
Can you show us what you see? Or share the scenario so we can troubleshoot?
A 410 HTTP error indicates gone, meaning the item or resource you are targeting doesn’t exist anymore.
Thanks!
Cheers,
Henk
1 Like
Any clues of what changes i need to make and where? I am not the one who set this up and the person isnt available anymore. I am currently looking for someone who could fix issues when i have it with make.
The message “the bundle did not pass through the filter” is just an information about which routes the flow did not take, because the conditions were not met.
The one that did pass through the filter was the Studios K1A route and that one resulted in the error 410.
Judging by what you said about lack of maintenance and without seeing the configuration of the Todoist module, my best bet is that your scenario is calling a retired version of the Todoist API.
If that’s the issue, you simply need to reconfigure the Todoist modules to to the latest API version.
Unfortunately i have no clue how that is done, however i am willing to pay for it to be done 
No problem. You can post a request on the Hire a Pro section or you can DM me you need a quotation.
Maybe the person who built the scenario left documentation on how to update it? That’s the kind of deliverables you should be looking for.
Please send me a quotation and time frame. My setup is relatively simple, however it isnt something i can do.
Hello @Agota_Luksaite, Welcome to the Make Community!
If you see those little double green up arrows on the Todoist modules, that indicates an updated version of the module is available. You can click that to upgrade the module which should use the new Todoist endpoints. You may wish you clone your scenario first just to be safe. Hope that helps!
im pretty sure i screwed up the connection to todoist (now i need the client id key and the secret key) to reconnect.
Also when i try to clone it says:
I haven’t gone through the upgrade in a while but I suppose in some cases you’ll have to reconnect to the service, in this case Todoist.
As for cloning the scenario, it’s fine, you’re creating a new and separate Webhook for the new scenario. Since you haven’t used the original Webhook in a while it was disabled so you’ll need to create a new one anyway if that’s still how you want to trigger your scenario.
Thanks to everybody for comments and help offers. I was shown how this works and fixed it myself. It is actually relatively simple and im glad i can do it on my own now.
2 Likes