Menu

TU/Toodledo - SynchronizerHttpException: Too Many Requests

Anonymous
2014-10-27
2015-01-13
  • Anonymous

    Anonymous - 2014-10-27

    Hi all,

    Having recently updated to version 4.3.3, I now am unable to Sync with Toodledo as I receive the following message at the Tasks sync stage :

    SynchronizerHttpException: Too Many Requests

    Please keep me posted, as local backup tend to limit my usage (multiple desktops & dgtgtd on android)
    Best regards,
    Eric

     

    Last edit: Anonymous 2014-10-27
  • Anonymous

    Anonymous - 2014-10-29

    I've had the same error. I went into settings and made sure ToodleDo was listed and had the correct login.

    Now I have another error (no name) that will not synch. I'm thinking of going back to TaskUnifier 4.3.2

     

    Last edit: Anonymous 2014-10-29
  • Anonymous

    Anonymous - 2014-10-29

    I uninstalled 4.3.3 and then installed 4.3.2. This did not help the synch error. I still have the same synch error.

    Any guidance on how to fix this error would be appreciated.

     
  • Anonymous

    Anonymous - 2014-10-29

    Don't forget to create daily backups. I'm sure the author works on this and the next 4.4.0 version shall tackle new Toodledo behaviour & APIs.

    Eric
    (even though we do have the ability to pick the new, home-brew sync-engine that Benjamin has developped to free ourselves of such API suprises, I'm sure Toodledo support cannot be spared for some time, naturally)

     
  • Benjamin Leclerc

    You can't rollback by just installed a previous version.
    If you want to use 4.3.2, then you have to delete the plugins folder in your data folder.

    Aparently, the latest version of the plugin I have released with the new API seems to work better.

    This API is new at Toodledo and is new at TaskUnifier side, I knew there would be problems, but anyway this new API will soon be the only one accepted by Toodledo, so I had to make the change at some point in time.

     
  • Anonymous

    Anonymous - 2014-11-01

    Hi Benjamin:
    just updated to tyne new version 4.3.3 and everytime it synchronizes it asks for the code from the Toodledo web page. Since the frequency of scheduled syncs is set to 60 seconds it now comes back with this too many requests error.

    For the time being I have set the syncing frequency to 18000 or so seconds. What setting do I have to put in so that I do not have to enter the code every time the system wants to sync with Toodledo.
    Thanks for your feedback

    Achim Schmidt

     
  • Anonymous

    Anonymous - 2014-11-03

    Hi,

    If it asks for a new code each time, it's probably that you still face the BadRequest error.
    For the moment it seems to be an issue at Toodledo side.
    The workaround is to enter a new code when it happens.

     
  • Anonymous

    Anonymous - 2014-11-03

    Hi all,

    Having updated the Toodledo plugin to version 9.5 (thank you Benjamin), I now encounter the following, somehow clearer error message :

    Message:
    com.leclercb.taskunifier.api.synchronizer.exc.SynchronizerHttpException: Too Many Requests: <error id="3">Too many requests. The app is now rate limited for 1 hour.</error>
    Level:

    So, I shall reconnect every 65 min all day long to check if that makes it for all my resync needs & fallback in smooth behaviour. Hoping that the resync is indeed progressive and that past progress is kept, not taken over & over again... I shall keep you informed.

    I wonder though if this limitation is compatible with full Toodledo resync for instance.

    I suppose Toodledo has something to do with this limitation, and shall not miss the opportunity to push them for platform & network upgrades...

    Have a good day.
    Eric

     
  • Anonymous

    Anonymous - 2014-11-04

    Hello,

    Today, I went as far as the "Synchronisation" window showing : "Synchronisation de 7508 Tâches" (message unseen so far since this initial post). Then the "Too Many Requests" message with 1 hour rate limitation...

    I'll go on in 65 minutes to check if this figure decreases.

    Also observed in menu Help / Get the Logs that I can access a zip files with 4 log files.


    Recent Log extracts :
    ...
    Java Version: 1.6.0_45
    Java Home: C:\Program Files (x86)\Java\jre6
    OS Name: Windows 7
    ...
    4 nov. 2014 10:44:42 com.leclercb.taskunifier.gui.processes.synchronization.ProcessSynchronize done
    INFO: Synchronization ended
    ...
    3 nov. 2014 11:10:04 com.leclercb.taskunifier.plugin.toodledo.calls.AbstractCall callGet
    ATTENTION: 429: Unknown
    3 nov. 2014 11:10:04 com.leclercb.taskunifier.gui.processes.synchronization.ProcessSynchronize$7 call
    ATTENTION: Unknown: <error id="3">Too many requests. The app is now rate limited for 1 hour.</error>
    com.leclercb.taskunifier.api.synchronizer.exc.SynchronizerHttpException: Unknown: <error id="3">Too many requests. The app is now rate limited for 1 hour.</error>
    at com.leclercb.taskunifier.plugin.toodledo.calls.ToodledoErrors.throwError(ToodledoErrors.java:174)
    ...
    4 nov. 2014 10:22:51 com.leclercb.taskunifier.plugin.toodledo.calls.AbstractCall callGet
    ATTENTION: 401: Unauthorized
    4 nov. 2014 10:24:13 com.leclercb.taskunifier.gui.processes.synchronization.ProcessSynchronize$7 call
    ATTENTION: Error while parsing response
    com.leclercb.taskunifier.api.synchronizer.exc.SynchronizerParsingException: Error while parsing response

     
  • Anonymous

    Anonymous - 2014-11-04

    Now "Synchronisation de 7519 Tâches" : task number NOT decreasing. I thus doubt the sync process will converge unless an updated API / Plugin is issued.

    Any suggestions ?

    Best regards,
    Eric

     
  • Benjamin Leclerc

    Did TaskUnifier asked you to enter an auth code multiple times during the sync ?
    Or only once at the beginning ?

     
  • Anonymous

    Anonymous - 2014-11-04

    Hi Benjamin,

    Well, as a new feature to authorize the plugin at Toodledo website, indeed only after plugin installation, when triggering the sync, I had to authorize twice, as I recall.

    So indeed at
    https://www.toodledo.com/active_apps.php

    I can observe double lines :
    TaskUnifier
    http://www.taskunifier.com Oct 22, 2014 Block
    TaskUnifier
    http://www.taskunifier.com Oct 22, 2014 Block

    Feel free to ask for additional details on my config, error reproduction case, User Id, etc...

    Eric

    P.S. :
    - As a Toodledo Gold subscription user, please don't hesistate to tell me how I could push Toodledo to help you, anyways ;)
    - as a first step, I've set "excellent (rated on Nov 04, '14)" onto
    https://www.toodledo.com/tools/directory_item.php?appid=taskunifier&rating=4

     
  • Anonymous

    Anonymous - 2014-11-04

    Additional info from https://www.toodledo.com/activity.php

    IP Address Description Date/Time
    IP@ Returned. Already signed in Nov 04, 2014 5:43 pm
    IP@ Successful signin Nov 04, 2014 5:43 pm
    IP@ Third-Party App Access (DGT-GTD) Oct 27, 2014 12:24 pm
    IP@ Third-Party App Access (TaskUnifier) Oct 22, 2014 10:47 am
    IP@ Returned. Already signed in Oct 22, 2014 10:47 am
    IP@ Third-Party App Access (TaskUnifier) Oct 22, 2014 10:46 am
    IP@ Successful signin Oct 22, 2014 10:46 am
    IP@ Third-Party App Access (TaskUnifier) Oct 22, 2014 9:47 am

    I'm sure that since Oct 22nd, I've triggered many a Sync attempt, which do not seem to have made their way up to this report page... strange enough.

    Eric

     
  • Anonymous

    Anonymous - 2014-11-04

    Another precision : I have NOT enabled 2-Step Authentication on my Toodledo account, having read the following :
    "Any app that syncs with Toodledo will need to be updated to support 2-Step Authentication"

    Best regards,
    Eric

     
  • Benjamin Leclerc

    Hi,
    Thanks for the info, I still don't know why it works with most of the users and not with the others.
    For example, I'm using TaskUnifier of course and never faced the token problem...

    The 2 step auth is another thing, the new api only uses OAuth, so 1 step auth.

     
  • Anonymous

    Anonymous - 2014-11-14

    Thanks for the post Benjamin.

    I observe less using TaskUnifier since the sync cannot work to the end and this saddens me thoroughly :(

    I wish I could sync again soon enough & wish you luck & courage to fight against this API (?) trouble.

    Of course I'd be too glad to contribute with additional info & testing at demand

    Best regards,
    Eric

    P.S. today's sync trace :

    Erreur
    
    Message:
        com.leclercb.taskunifier.api.synchronizer.exc.SynchronizerHttpException: Too Many Requests: <error id='3'>Too many requests. The app is now rate limited for 1 hour.</error>
    Level:
        WARNING
    Stack Trace:
    Too Many Requests:  Too many requests. The app is now rate limited for 1 hour. 
        com.leclercb.taskunifier.plugin.toodledo.calls.ToodledoErrors.throwError(ToodledoErrors.java:174)
        com.leclercb.taskunifier.plugin.toodledo.calls.AbstractCall.throwResponseError(AbstractCall.java:186)
        com.leclercb.taskunifier.plugin.toodledo.calls.AbstractCall.callPost(AbstractCall.java:162)
        com.leclercb.taskunifier.plugin.toodledo.calls.AbstractCall.callPost(AbstractCall.java:117)
        com.leclercb.taskunifier.plugin.toodledo.calls.CallEditTask.editTasksMax(CallEditTask.java:257)
        com.leclercb.taskunifier.plugin.toodledo.calls.CallEditTask.editTasks(CallEditTask.java:55)
        com.leclercb.taskunifier.plugin.toodledo.calls.ToodledoStatement.editTasks(ToodledoStatement.java:530)
        com.leclercb.taskunifier.plugin.toodledo.ToodledoSynchronizer.updateModels(ToodledoSynchronizer.java:508)
        com.leclercb.taskunifier.gui.plugins.AbstractSynchronizer.synchronizeModels(AbstractSynchronizer.java:441)
        com.leclercb.taskunifier.gui.plugins.AbstractSynchronizer.synchronizeModels(AbstractSynchronizer.java:126)
        com.leclercb.taskunifier.plugin.toodledo.ToodledoSynchronizer.synchronize(ToodledoSynchronizer.java:156)
        com.leclercb.taskunifier.gui.processes.synchronization.ProcessSynchronize.execute(ProcessSynchronize.java:252)
        com.leclercb.taskunifier.gui.processes.synchronization.ProcessSynchronize.execute(ProcessSynchronize.java:71)
        com.leclercb.taskunifier.gui.processes.Worker.doInBackground(Worker.java:176)
        javax.swing.SwingWorker$1.call(Unknown Source)
        java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
        java.util.concurrent.FutureTask.run(Unknown Source)
        javax.swing.SwingWorker.run(Unknown Source)
        java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        java.lang.Thread.run(Unknown Source)
    
     

    Last edit: Anonymous 2014-11-14
  • Anonymous

    Anonymous - 2014-11-14

    I also am having problems with the Toodledo authorization code not being accepted on recent upgrade to 4.3.3; have tried uninstall/reinstall to no avail.

    error Message:
    com.leclercb.taskunifier.api.synchronizer.exc.SynchronizerHttpException: Bad Request: <error id="102">Authorization code doesn't exist or is invalid for the client</error>
    Level:
    WARNING
    Stack Trace:
    Bad Request: Authorization code doesn't exist or is invalid for the client
    com.leclercb.taskunifier.plugin.toodledo.calls.ToodledoErrors.throwError(ToodledoErrors.java:174)
    com.leclercb.taskunifier.plugin.toodledo.calls.AbstractCall.throwResponseError(AbstractCall.java:186)
    com.leclercb.taskunifier.plugin.toodledo.calls.AbstractCall.callPost(AbstractCall.java:162)
    com.leclercb.taskunifier.plugin.toodledo.calls.CallOAuth.getToken(CallOAuth.java:64)
    com.leclercb.taskunifier.plugin.toodledo.calls.ToodledoStatement.getToken(ToodledoStatement.java:58)
    com.leclercb.taskunifier.plugin.toodledo.ToodledoConnection.connect(ToodledoConnection.java:111)
    com.leclercb.taskunifier.gui.processes.synchronization.ProcessSynchronize$4.call(ProcessSynchronize.java:197)
    com.leclercb.taskunifier.gui.processes.synchronization.ProcessSynchronize$4.call(ProcessSynchronize.java:193)
    java.util.concurrent.FutureTask.run(Unknown Source)
    java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    java.lang.Thread.run(Unknown Source)

    end message

     
  • Anonymous

    Anonymous - 2014-11-15

    For those who can't still connect, I suggest to go reinstall to 4.3.2.
    But to make this work, you have to delete the content of the folder "plugins" which is inside your TaskUnifier data folder.

    The data folder of TaskUnifier can be found in Help -> About -> System -> Data folder.

    So, in that folder, go in "plugins", and delete all the files (ending with .jar).

     
  • Anonymous

    Anonymous - 2014-11-19

    After last suggestion I finally rolled back to v4.3.2.

    My sync attempt lead to the following error tough

    Eric


    Erreur

    Message:
    com.leclercb.taskunifier.plugin.toodledo.calls.exc.ToodledoConnectionException: La cl� d'authentification que vous avez sp�cifi�e est invalide ou a expir�
    Level:
    WARNING
    Stack Trace:
    La cl� d'authentification que vous avez sp�cifi�e est invalide ou a expir�
    com.leclercb.taskunifier.plugin.toodledo.calls.ToodledoErrors.throwError(ToodledoErrors.java:126)
    com.leclercb.taskunifier.plugin.toodledo.calls.ToodledoErrors.throwError(ToodledoErrors.java:145)
    com.leclercb.taskunifier.plugin.toodledo.calls.AbstractCall.throwResponseError(AbstractCall.java:206)
    com.leclercb.taskunifier.plugin.toodledo.calls.AbstractCallTask.getResponseMessage(AbstractCallTask.java:92)
    com.leclercb.taskunifier.plugin.toodledo.calls.CallEditTask.editTasksMax(CallEditTask.java:262)
    com.leclercb.taskunifier.plugin.toodledo.calls.CallEditTask.editTasks(CallEditTask.java:55)
    com.leclercb.taskunifier.plugin.toodledo.calls.ToodledoStatement.editTasks(ToodledoStatement.java:558)
    com.leclercb.taskunifier.plugin.toodledo.ToodledoSynchronizer.updateModels(ToodledoSynchronizer.java:508)
    com.leclercb.taskunifier.gui.plugins.AbstractSynchronizer.synchronizeModels(AbstractSynchronizer.java:441)
    com.leclercb.taskunifier.gui.plugins.AbstractSynchronizer.synchronizeModels(AbstractSynchronizer.java:126)
    com.leclercb.taskunifier.plugin.toodledo.ToodledoSynchronizer.synchronize(ToodledoSynchronizer.java:156)
    com.leclercb.taskunifier.gui.processes.synchronization.ProcessSynchronize.execute(ProcessSynchronize.java:252)
    com.leclercb.taskunifier.gui.processes.synchronization.ProcessSynchronize.execute(ProcessSynchronize.java:71)
    com.leclercb.taskunifier.gui.processes.Worker.doInBackground(Worker.java:176)
    javax.swing.SwingWorker$1.call(Unknown Source)
    java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
    java.util.concurrent.FutureTask.run(Unknown Source)
    javax.swing.SwingWorker.run(Unknown Source)
    java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
    java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    java.lang.Thread.run(Unknown Source)

     
  • Anonymous

    Anonymous - 2014-11-25

    While backuping my up-to-date, no syncing TaskUnifier PC, then upgrading TU 4.2.1 to 4.3.2 on another PC then restoring the backup onto this latter, Sync occurred 3 times with fewer and fewer remaining tasks to be synchronized each time before error. Finally this new PC succeeded to reach a state aligned with Toodledo... Note : this PC has ADSL connection

    Well, maybe I'll get to the same results on my main PC, eventhough so far error "La clé d'authentification que vous avez spécifiée est invalide ou a expiré", after some minutes, while "Synchronisation de 7233 Tâches". Note : this PC has wifi/3G connection.

    Shall keep you informed.
    Eric

     
  • Anonymous

    Anonymous - 2014-11-25

    Hi again : new message observed on not-syncing PC (TU 4.3.2) :
    Eric


    Erreur

    Message:
    com.leclercb.taskunifier.plugin.toodledo.calls.exc.ToodledoApiException: Nombre maximum de jetons atteint. Votre application a demand� trop de jetons dans une courte p�riode de temps. Vous devriez le sauver et l'utiliser jusqu'� ce qu'il expire
    Level:
    WARNING
    Stack Trace:
    Nombre maximum de jetons atteint. Votre application a demand� trop de jetons dans une courte p�riode de temps. Vous devriez le sauver et l'utiliser jusqu'� ce qu'il expire
    com.leclercb.taskunifier.plugin.toodledo.calls.ToodledoErrors.throwError(ToodledoErrors.java:128)
    com.leclercb.taskunifier.plugin.toodledo.calls.ToodledoErrors.throwError(ToodledoErrors.java:141)

     
  • Anonymous

    Anonymous - 2015-01-05

    Happy New GTD Year !

    UP of my above posts ;)
    Eric

     
  • Anonymous

    Anonymous - 2015-01-12

    Well, I decided to act on this, at the user end, and finally stabilised the situation :
    1) have an acceptable TU backup at hand
    2) clean Toodledo account
    --- Backup from Web page
    --- remove all items but one in each category -tasks, folders, ...- in backup file
    --- Restore this tweaked backup file to toodledo
    --- manually clean up the last tasks, folders, etc...
    3) restore the acceptable backup onto a 4.3.2 TU
    4) "Copy all data" from TU to Tooldedo, as a sync option

    At this stage, you should have a clean ToodleDo account, there only remains to clean all data and retrieve the reference Toodledo version on all your environements (Clean all & Synchronise)

    That's it
    Eric

     

    Last edit: Anonymous 2015-06-18
  • Anonymous

    Anonymous - 2015-01-13

    I went back to 4.3.1 and was able to get in with no issues; had similar errors with 4.3.3

    I totally wiped out the folder that had TaskUnifier in it and the data folder in Roaming -- Windows 7 set up

     

Anonymous
Anonymous

Add attachments
Cancel





Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.