Why does my tags keeps getting disabled by the system?

Question

I have to re-enabled the tags several times, the issue doesn't seems to fix itself. The tag keeps getting disabled by the system - checker works fine when enabled, but after a short while, it got disabled. Anyone has any idea?

Comments

That does not happen to me, I have not head that it is done automticaly.
Only automation like that is that identical duplicate tags(gc code and config) on the same script are automaticlay removed.
But there is a bug that has happens sometime to me and that is that the state of the enable button and the resulting status of the tag is the opposit. I think it happens when you edit multiple tags. Reloading the page solves the problem.
That might be the problem. I have not been able to replicate it in a Constanta way

Answer 1

There is no automatic disabling of tags (yet). I can only see two reasons (and maybe what Target mentions, which I wasn't aware of).

1) When implementing auto-challenge-checkers we found that some scripts took several gigabytes of memory for some users. We then disabled the tags which had issues. I think there has been 2 unique tags disabled in that phase, one of them disabled once and one of them disabled twice. This is 1-2 months ago. So I doubt this is the reason.

2) If someone else owns the script, he/she can edit your tags as well, including disabling them. If that is the case, I would suggest that the script owner leaves a comment in the tag comment field when doing so. That he hsa done it could be because it isn't correct, or that it fails to run on some users and turns up on his "My issues"-list.

Adding the relevant tag id to your post could maybe help us to figure it out.

Comments

Thanks, I've asked the script owner, he did not disable my tag. This morning, I re-enabled the tag, by evening, it was automatically disabled.

My checker is for Cache GC5JZ1P - The Lost Symbol. Is this the tag ID?

---

8061 is the ID of that tag (this is partly a note to myself).

I also thought of another reason for tags to be disabled. If there are two identical tags the newest will be disabled. This does not seem to be the case either. I will investigate some more.

UPDATE: It is our housekeeping that thinks it's a duplicate, but from what I can see it is not. I'll get back to you when I know more. While I am investigating it might be enabled and disabled a few times.

---

This tag is getting disabled because Project-GC does not think GC5JZ1P is a challenge cache, and the tag references it.

According to Groundspeak's guidelines a challenge cache MUST contain the word "challenge" in the cache name. I would suggest renaming the cache (adding " - Challenge" or prefixing it with "Challenge - "), to actually follow the guidelines. The reviewer should not have published this geocache since it is not allowed to have ALR (Additional Logging Requirements) without having that word in the title.

However, if you feel that you do not want to rename it, I can fix an exception in Project-GC for you.

---

Hi Ganja1447,

Would you help me add an exception for this tag? I am extremely grateful for your help.

I delete the old tag and re-create a new one, the new ID is 11267.

Many Thanks!

---

Sorry about the delay. I am drowning in work. I will fix this today, so from now on it should not turn off again. (ID = 11267)