[Bug] Community Celebration Event got archived automatically

[+badehaubendealer]

Hi guys,

 

my Community Celebration Event (GC8Q97T) was archived automatically by the Geocaching HQ Admin. This was the log:

 

Quote

This old, unpublished cache has been archived as part of site maintenance and database clean-up. You are not required to take action. If you are working on a new cache, create a new listing and submit it for review. Should you prefer to use this listing, contact your local reviewer to request unarchival. See this Help Center article to identify the reviewer for your area. In the future, please work to submit cache pages for review within three months of creation. If you are working on a complex cache, or are waiting on permission, communicate your progress by posting regular reviewer notes to unsubmitted listings. Submissions older than six months may be automatically archived.

 

I understand that unused listings get archived, but these events are allowed until the end of 2021. I don't think they shoould be archived after three (or six) months. Seems like a bug in the Geocaching HQ Admin

Edited August 26, 2020 by badehaubendealer

[+werla]

Did you contact you local reviewer? He can unarchive the listing.

[+badehaubendealer]

I did not do that yet, but I will.

 

However, the intention of my post is not to get my event un-archived. The intention is to point out that there may be a bug in the Geocaching HQ Admin automation. That bot probably should not archive Community Celebration Events until the end of 2021.

[+Bl4ckH4wkGER]

The automation currently does not differentiate between cache types so this is not a bug.

 

I will look into excluding Community Celebration Events going forward because of the extended timeline. At the same time it is your responsibility as a cache owner to keep listings from falling into this automation, too. You can do that by editing the listing and or posting logs on it.

[+badehaubendealer]

Thank you for the quick reply, and thank you for the explanation. So what you're saying: It's not a bug, it's a feature?

 

I didn't know that this belongs to my duties, so tahnk you for pointing that out. I will make sure this won't happen again.

 

From my perspective, this topic can be closed. Again, thank you!