I guess PR told you there was a cache in the queue (the lurker) for your location? How else would you know?
Is this the cache you've been having so much trouble with? I guess the lurker must be your cache thief!
But do you think these difficult to place locations you currently have are being lurked on that much? And, in reality, PR would get pissed that someone keeps submitting, as it will keep coming up in the queue when there is an existing cache there. That will only be tolerated so long. They send back to the submitter and after a while I presume would just archive the submission -- unless the cache is gone.
I just don't imagine that strategy working very well. Not for the choo choo series.
I think you're missing the point of my post. Assuming you submit the new cache and archive the existing cache in the same day. If there's a lurker who has submitted a cache at your location earlier and just standing by, they'll get your location, because you just created the replacement and he submitted his earlier, so he's ahead of you in the queue.
HC - I've had several I had been working on over the years have that happen. Surprised it took so long, too.
Thot - The easy way for this to submit your new cache at the same location and then archive the old. Your new cache is already in queue when you archive it (even if minutes before) and any lurker will have a submission in queue after yours. Never had an issue.