Some many months ago, my sync stopped working correctly for long periods of time. It doesn't sync automatically at all anymore even though it still should, but even when I manually click on sync, it usually stops/quits after awhile before finishing. After a lot of trying to figure out what was going on, I finally did. Whenever I have a lot of hits on one day, say more than 500 or so, then the sync goes so fast that it triggers mturk not allowing it anymore and when I go back to mturk I have to do a captcha and all that to get back in. So, the sync goes too fast for whatever limit mturk has now, when I have any substantial amount of hits. The thing is, once I have a day with that many hits, it triggers the stop/quit almost every single time from then on, until that day finally drops off from being a day that is synced. Syncing goes back I think like a month and a half or so, so syncing won't work for like a month and a half after I have a day with a lot of hits. The even worse thing is, I usually have a day with a lot of hits at least once within a month and a half, meaning I can almost never sync my hits anymore. Sometimes I get lucky and it will finish (like really rarely, like once ever two months or so) but that's it. It seems like it could be an easy fix if I knew how. It seems like however fast the program is scheduled to check hits, just slow it down. I know this would make sync slower for me, but that's way preferable to it never working. I don't mean it needs to be changed for everybody if theirs works, but maybe there's some way I can go in and change the script manually just for me to make it slower? The problem is I don't know much about that type of stuff and I've really tried looking everywhere so many times and can't figure out how to do this. @Kadauchi because I think you would know really quick how to do this, but also anyone else who might be able to help. Thanks!
It's from too many page requests in a short amount of time. The CAPTCHA seems to be on a timer, so once you trigger it, you should be good for a short period of time. Are you not already triggering it on batches? As I am sure you have witnessed, it's different from the CAPTCHA triggered by HITs. I would sync right after if you are at a good point. I personally use QBC to trigger the CAPTCHA by running multiple 7 day syncs in a row until it pops. After I reset it, I have no issues syncing both QBC and MTS, even on heavy days. The nice thing is Kada set MTS to automatically swap HITs over to paid after 45 days, but that does sort of defeat the purpose of having "real-time" stats.
