Hi all! Yes, the batch was pulled as a part of the support ticket. The ticket has been completed. My dashboard is now loading much, much faster, so hopefully in one minute when I hit "go" everything works faster for you as well. They had to restart my instance in order to improve speeds but I'd stepped out for lunch.
It's amazing that you put forth as much effort as you do into this. If there was a requester of the month award, you'd be in line for it
Hi all - the support folks did great work but it did trip up the batch, so I will need to reload which generally takes some time. Should be back up and working at full speed within the hour, but I do have a meeting this afternoon so hopefully that doesn't interrupt.
FOUND THE SOURCE OF THE PROBLEM!!!!! fixing it now but I desperately need coffee, perhaps you will all forgive me
So this is the fix to keep it from getting bogged down? There have been so many fixes I've lost track.
Question on these upcoming quals: Are you going to create qualification HITs for it, or is it just going to be auto-assigned to those of us who've stuck around? Just curious, because well, I've been inactive on the forums as of late, but I've also done almost every batch you've posted since you started posting, so I'm hoping to snag it. Cuz, ya know, ABQ and such.
I think she means that all the new people requesting it will get it later in the week after the "loyal" workers (you) get to do a few since they hung in there.
I'm actually OK with this pretty sure this will give me almost the exact amount of time needed to finish the OCMP5. I feel like OCMP likes me they really really like me.
Yes, exactly. I'm not changing any quals that already exist, just trying to give a few batches to workers I already have as a small "thank you" for putting up with my antics.
LOL every hour a new fix. Yes. I believe I've identified an issue with our storage security credentials which limited calls to x per minute, which was bogging down the system. I'm transitioning back to the old storage method for now, because it's not that important even for the backend. This will also fix the problem where the tasks where incorrectly batching HITs (find the homepage should have 2 records, not 1).
There are! I'm not sure why those are still showing up, but I think it will give you an error if you try to do them. This is lag on Amazon Requester's end, IIRC.
