I get this error all the time. I have one todo note that should just make 3 requests every time it loads, but I often only see these errors. Is the plugin making more requests than it needs or is Todoist just really strict with how many requests they allow?
I am getting this error also - I think there must be a new bug/malfunction/unhelpful setting somewhere in Obsidian, the plugin or at Todoist (I suspect the latter), because I wasn’t getting this error previously.
The plugin seems to have stopped working altogether now, even after waiting a number of minutes to let any timed limit expire. Can’t get it to work on WIndows, iPhone or iPad. Earlier I was able to get it to work but it was reporting “Unknown project” against each to do item.
Maybe there is not enough bandwidth on the Todoist server. I am going to try to raise a query with them.
I have lodged the following support request with Todoist:
"Obsidian Todoist plugin is reporting a 429 Too Many Requests error. I am using it via the API. It was working earlier today. Then it kept saying that the project was unknown. Now it is not working at all and says “Error: Too Many Requests or on iPad it refers to Request failed, status 429. I have tried waiting a while but still not working. I have been on the Obsidian forum and apparently I am not the only one experiencing this error today. It something up with your server?”
Another user reported this:
“I was having the same issue and I increased my Auto Refresh Interval in the module’s settings from 60 seconds to 600 seconds. I did it just a day or two ago but it has been stable since then.”
Rigmarole, hi. I did ask Obsidian whether they could assist, via their support facility, assuming wrongly that when a plugin was on the Obsidian site there would be a conversaition between Obsidian and the developer and/or the party whose API was being used. They politely put me straight. A noob error, but thanks for pointing it out. There is already an issue logged on Github, though no-one (including the developer, who had already commented, and was anticipating a possible update) was clear on the cause of the problem. I asked Todoist if there was something up with their server. They looked at their logs and offered to discuss the issue with the developer with a view to finding a solution. I passed that offer onto the developer.