I had put a new nomination On Hold as I wanted to use an Upgrade on it, however after releasing the hold and setting it as “Upgrade Next” it got Accepted by the Niantic Team. It’s still marked as Upgrade Next however. Does this mean that the next Upgrade will still be applied to it although it’s already Accepted, wasting the Upgrade?
As long as it’s “next” no Upgrade has been applied, and I don’t think the next one you earn can go to an already resolved nomination.
I would however suggest disabling this setting and applying Upgrades manually as you earn them by just using the Upgrade button instead. Instructions on how to do that in this post:
This setting is even less relevant currently, with fast resolutions by ML, the team or the community now a possibility. If you are looking to Upgrade something, I would wait a couple of days before doing so, because the exact same thing you mention above could happen to an Upgraded nomination and it does indeed sting to lose the Upgrade on something that got a fast resolution anyway. Think of Upgrades as of something that is for nominations that are in it for the long haul.
Ive even had the ML take stuff that had been in queue for over a week, so it seems a bit pot luck. Ive been upgrading things that are already in community voting, or just deciding to “waste” the upgrade regardless
But yeah I do not use “upgrade next” as I have auto-upgrade disabled and I much prefer it thar way
It definitely happens, to me too (and it shouldn’t), but the ML grabs that happen shortly after release coupled with the unclear Upgrade Next feature as discussed in the post above are the main danger to newer reviewers imo.
I did an experiment to test. I marked a nomination “Upgrade Next” but never upgraded it. The “Upgrade Next” tag did not go away immediately after it was accepted, but it did go away.
I would definitely turn “Automatically apply upgrades” to off though, just to be sure that the system won’t glitch.
Thank you for your reply. I’ll make sure to go turn the setting off. I thought it was simply always on with no way to turn it off.