AW sometimes miss few asana tasks while fetching

[adishap]

AW sometimes miss few asana tasks while fetching,Due to those missed tasks, tasks are deleted from taskwarrior and when AW syncs next time it tries to delete tasks from asana which are deleted from TW and if -delete flag is less than number of tasks to be deleted, it stops execution else it deletes tasks from asana as well. To restart AW we need and stop mass deletion we need to delete data from .tasks and start it again.

Logs Attached.

Starting sync at 2016-12-14 03:09:18.727802874 +0000 UTC
        Asana results found: 794 active
  Taskwarrior results found: 794 active, 2 deleted
All synced up. DONE.

Starting sync at 2016-12-14 03:10:18.727804434 +0000 UTC
        Asana results found: 658 active
  Taskwarrior results found: 794 active, 2 deleted
Delete from Taskwarrior: ["<task name>"]
Delete from Taskwarrior: ["<task name>"]
.
.
.


Starting sync at 2016-12-14 03:11:18.727795868 +0000 UTC
        Asana results found: 794 active
  Taskwarrior results found: 658 active, 138 deleted

==========================================
Task deletions requested from Asana : 136
Max allowed per sync                : 5
Most likely this is a mistake!
If so, please run 'rm -f ~/.task/*' to clean up Taskwarrior (or wherever else you store it's state).
If you genuinely want to delete all these tasks, then set the 'deletes' flag to a higher value.
Crashing to avoid mass deletes from Asana!
==========================================

[manishrjain]

That is strange. Seems like an issue with Asana's APIs or something.

[adishap]

@manishrjain might be the case but it is occuring really frequently.

[manishrjain]

hmm... I don't see it happening on my machine. Any way to reproduce?

Could have something to do with pagination.

[adishap]

No I dont know how to reproduce it. It automatically happens, might be an asana issue. I think it might be possible due to issue-19 previously in case of error in asana api it stopped execution and now so it checks http.status_code and it does not stops execution but still tasks are not fetched. Not sure about it.