I'm not sure if this is a bug, or not; tagging in case it is.
I find the Challenges signed (but not yet logged as found) to be a great way to keep track of challenge caches I am working on.
However, it seems that it does not run the checkers for any of the challenges. The red "unqualified" mark only changes to the green "qualified" mark if I manually run the checker itself. There have been several times where I have lost track of a challenge that I qualify for, and this page never seems to update to a green check to let me know.
I previously left a challenge I knew I'd qualified for sit for several days to see if the page would update itself, but it never did until after I'd run the checker. Even then I think I had to wait a day or two.
Today's example:
I've been working on qualifying for GC9KJ1T for a while. This morning, I logged the last D/T combination I need to qualify, GC11NCM. I waited until this afternoon, to ensure that Project-GC "knew" that I had logged GC11NCM. It did - I can see it as the latest in my milestones.
When I go to the challenges tab, however, it still shows that I'm not qualified for GC9KJ1T.
Then I run the challenge checker, and, yes, I'm qualified.
Going back to the Challenges signed (but not yet logged as found), I refresh the page, and...it's still not showing I qualify.
When, if ever, does the system run the checkers on these challenges I have signed to see whether I qualify? Or must I always do it manually? Is this by design, or is this a bug?
Edit: 12 hours after posting this, and after refreshing the challenges tab twice again, I now see a green check. So, the process seems far from automatic.
