@JL_Fitzpatrick: We can’t control the sync behaviour of Insync client from our end. We haven’t released any auto-update in the past 3 days either. Sometimes, the files in the queue may seem stuck when Insync is busy with higher priority tasks such as local folder scan (just after it starts or resumes) or processing the Google Drive change events. Therefore it is advisable that you do not pause/force-sync often if you have a large number of files being sync’d locally. We are working on improving this behaviour.
In some recent reports, we have observed that for some of the users, making a few changes to certain folders leads to a LOT of Google Drive metadata change events where the actual data hasn’t changed. This also causes Insync to get busy doing “nothing” as it processes those events and finds out that not many files have actually changed. It seems to be an issue with some specific Google Drive folders. We are still investigating the issue and are not sure yet if it can be circumvented by Insync.
If you experience “not syncing” phase other than after you have just resumed/started Insync, please send to us the logs and compressed copy of the Insync databases folder (present next to the logs file): How to find the log files (Do not quit Insync, just create the copy while it is still running)
Thanks.