Jump to content


Photo

Toodledo excessive api usage error

Toodledo api error

  • Please log in to reply
2 replies to this topic

#1 SH4D0K1NN

SH4D0K1NN

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 03 November 2013 - 08:46 AM

Keep getting a excessive api error when due today syncs. Started the other day and I waited it out because I know there is a limiter every hr from toodledo but it has been 2 days and every time it tried to sync I get the error and obviously it hadn't sync to toodledo at all in this time. Is there a fix for this?
It first occurred I believe because I was cleaning up a bunch of my tasks over a short period and that's when I first got the error, but I thought it would clear itself...

#2 Chris

Chris

    Administrator

  • Administrators
  • 337 posts
  • LocationUtah

Posted 08 November 2013 - 02:42 AM

I'm in the process of tracking this down. I have a couple of theories, though. But, can I ask you a few questions about your setup?

 

First off, are you using both the Android and Windows clients? This is relevant because they share the same ToodleDo app key. This makes ToodleDo think that both programs are in fact the same app. I did this so that I could share additional meta-data between the two as the meta-data field is tied specifically to the app key (meaning if they had different keys then the meta-data would not be shared between the two programs).

 

Second, what is your sync interval set to? And, are you using the "sync immediately" option?



#3 SH4D0K1NN

SH4D0K1NN

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 11 November 2013 - 07:52 AM

Thanks for your reply.
I have it checked off to sync after change on phone and 4hr sync intervals.
I don't use the windows client. It was working OK until I did a clean up and must have triggered something either due to subfolders or syncing too much.
If it was syncing too much, wouldn't it be cleared by now? Just got the error today after checking off some items.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users