I just had a nomination automatically rejected around 2.5 days after submission. What makes this particularly frustrating is that I had only applied an Upgrade after the first 24 hours had already passed. At that point, I assumed the nomination had already made it through the initial ML review phase and would eventually be reviewed by the community.
Instead, it was automatically rejected after the Upgrade was applied.
This is not the first time I have observed this. I have had a similar case before, and I am starting to get the impression that applying an Upgrade may somehow trigger an additional ML review or another automated check. Of course, I cannot prove that, but the timing feels very suspicious.
My main concern is not the rejection itself. If the nomination is not eligible, then reject it. Reject it ten times if necessary. Thatâs not the issue.
The issue is that I am using a hard-earned Upgrade because I want the nomination to reach community reviewers faster, not because I want Emily to take another critical look at it after it has already been sitting in the system for more than 24 hours.
From a user perspective, this feels very unfair. If an Upgrade can still result in an ML rejection after the nomination has already been in the queue for days, then it feels like the Upgrade is being wasted rather than helping the nomination progress.
Has anyone else experienced something similar? Is there any known explanation for what is happening behind the scenes when an Upgrade is applied to a nomination that has already been waiting for more than 24 hours?
Iâd be interested to hear whether others have observed the same pattern.
Can you be sure it was the machine learning system that rejected? The email will say âour teamâ if it was pulled into internal (human) review and rejected.
Hello, yes I have had a nomination made on 30th May pulled into Niantic Review overnight. It seems the ML is going through nominations after the fact. There were reports of lots of âcoalâ seen in review yesterday and it has been considered that ML was not working for a period, as has happened before.
Thatâs very interesting. 30 minutes ago I got a nomanition from 30th may automatically rejected which was just in voting which shouldnât be possible and is completely ridicoulous in my opinion. This was not upgraded so I begin to assume that this could be a bug. The nomination I posted was also from 30th may
I think this is ML Working As Intended. It is supposed to have a chance to look at all nominations and make a decision based on its parameters, even those that have made it into voting already. If you had applied an upgrade you could have had a genuine grievance but luckily that was not the case here.
