Katy112 wrote: 
hamsou73 wrote:
@coated_pill
Probably you got an Ooops done by G.T.A a very long ago & been circulating also by G.T.A & finally reachs you .. so it comes from a very old ID & RF classes it as expired .. in that case you got "This Hit can not have jobs assign to it" msg. But this is my own observation 
BTW >> Where is our skilled CIA agent

You wanted to say a oops ( it's hit ) stolen by GTA users..is like a candy in a shiny foil,but when you unwrap the nice and shiny foil,the candy isn't there anymore...GTA ate them... 
LOL !!! That was hilariously funny Katy !
I like your candy foil example, however keep in mind oops can still be gold mine because eventually
it is the KEY to a new HIT when it becomes available.
Remember that hits comes from one central server, they are assigned to both CF and turk,
CF has a delay before it shows assignment links, on turk they appear first, so aside from GTA,
you also have turk users who might have done the hit already that was assigned to that
HIT ID. RF has a dynamic hit attribution - these links query the system for more hits, if none find, you get oops, however, they also have a set limit on the number of times a new HIT can be assigned to an older HIT ID #.
So here is what happens.
LINK assignment with HIT ID xxxxxxxx, person y gets the hit, but he nicely GTA it whilst completing the HIT.
This GTA'ed assignment link goes BACK in the pool and distributed to someone else, they get a hit, but GTA it too, and so forth, until the same link goes into circulation and gets converted to hits, (you see this cycle ?)
Now obviously RF is stuck because they cannot set the link to be used only one time as it would create
problems for even legit users.
So in theory, without GTA users, the oops would last far longer (its expiry is not in the form of TIMER, but in the form of CYCLES of use.) For example, a link with HIT ID could be used 10 times (just an example), after 10 hits were converted through the link it no longer could be used.
The assignment links are CF side, the whole process of generating a unique assignment link hash
is automated by script by RF side, NEW JOB IDs are created after a certain amount of HIT ID increments.
All automatically. So they don't automatically REMOVE the old links when they are returned to pool.
This is a process done automatically eventually during a cleanup cycle or can be called manually by
test author.