Thanks for that. I updated the script to version 0.3.12 which should fix this problem. Tell me if it does. Usually rolling back to an older version will work when problems like this happens for future reference to everyone.
Yes you can start your queue from anywhere and it should recognize the hit and make sure the next hit will be the next lowest timeleft in queue. To make sure it's working the tab title should show the timer and queue number when doing a hit.
Try rolling back to 0.3.9. Export the data and send me the .json file to my email: Johnnyrs@allbyjohn.com
I tried something else. I updated the script on this laptop 0.3.12 and it's working so it's something on the other one causing it. I could probably export the JSON from here and stick it over there and fix it (*maybe....*) but do you still want to look at it anyway (could be helpful, dunno)
Yes would like to look at it to see what data is causing it. If it's working on the laptop and not on your computer then it's the data that was saved in browser which isn't easy to get to or fix and the JSON file might not show it.
Actually I work in firefox and chrome so I understand this problem very well. You should only run 1 PC on your computer because even if you have nothing collecting, it is still checking the queue page every 40 seconds. That may not be a problem for Pre's because it's a long timer but it's not going to give you the most accurate fresh queue. The main PC that is collecting hits would be the most accurate so you should do as many hits in the browser you have PC running in. There is no communication between different browsers so doing hits in another browser won't communicate back to the main PC. If you need to work in another browser I would suggest keeping QOF for that browser. QOF does send 2 requests at the same time after every submit to grab the fresh queue so if you doing the hits in seconds that will cause a lot of Pre's. My new queue helper script doesn't send a request to mturk for the queue. It asks PC for that information. I might add a way for it to work without PC by requesting the queue in the background after a few seconds but it won't be as accurate. Even if I add a way to work without PC it should be better than QOF with the Pre problem.
Thanks. As I expected I didn't see any problems with the data and it worked fine on my computer. I hope it's working for you now. I think it worked on your laptop because you didn't update it to each of the other new versions. One of those versions saved a bad data. I am guessing another fix would have been go back to 0.3.9 export data and then import data. Then update to newest version. Maybe that would have deleted the bad data. Don't know. Someone else had the same problem too.
Well if you don't like the sound of it you can change the alarm to another nicer sound if you want from the options/alarms menu. You can also replace it with a blank audio file if you want. There is also a way to disable the captcha alert in the options/general but that will make the script not pause at all for a captcha. You would need another script to detect it and alert you to it.
Ok this is a known issue for a few because an updated version saved some wrong data.
I believe you already got your answer but for others click on the details button and look for "friendly requester name" and "friendly title". Change those to any names you want and the script will use those instead of the groupId or the real names. If you want the real names to show up after the script finds a hit you can just delete the friendly names and it will go back to the real names.
I to am having the same issue as
@catnapped . I tried to go back to 0.3.9 and but it' still not working for me. I haven't tested to see if any other scripts are interfering with it, but I just wanted to put it out there that I'm having this issue too.
Try the instructions I gave in this post: http://www.mturkcrowd.com/posts/436027/. Version 0.3.6 is before I added data to the database so I am hoping that will at least get past any data problems. If you have an older export you can go to the current version and reset the data. Then import the saved data file.I to am having the same issue as
I went back to 0.3.9 and it will work if I just continue anyway through it, but no luck with the most updated version.
Click on the details button for the job and see if there is a limit for the queue. If you don't want the limits then just put it down to 0. I left those limits there as examples for the zing/ibotta stuff because usually it's nice to have your queue open for better paying hits. It's up to you if you want a limit or not.
