Hi there - I suspect I know what's going on but this checker https://project-gc.com/Challenges/GCAEV95/81762 is timing out for one local cacher when he runs it. I'm guessing it's because of his high find count and the checker just runs out of time to do all the math. Is there any way to extend the 'allowed' run time or is there some other way to optimize the code so it works for him?

Or should I assume this is a one time thing because of his high find count and just assume he qualifies for the challenge? I'm already inclined to believe that anyways.

Thanks.

The checker times out between 75000 and 76000 finds.
The cachers I tested had on avarage had 10 times the required target.

Thank you for the information, vogelbird. This cacher is well over that threshold so that explains the time out issue. I've told him to go ahead and log the cache as a result.

Please go ahead and close this issue as resolved as well. I shouldn't come across this issue too often and I'll update the description to make people aware of this time out issue.

Thanks.