Submission "In Queue", cannot change to "On Hold" and cannot edit

Bug Reports & Technical Support
,
1

Bug Reports should include the following and any additional information you feel is necessary to aid in the investigation of the bug.

  • Description of the issue:
    Similar to others previously reported, I have been unable to mark the Wayspot in question as on hold or edit, and also cannot apply an upgrade. I have tried reloading the page and this has not changed the issue.

  • Date first (or most recently) experienced:
    11/10/2024

  • Wayspot name & location:
    The Masons Arms
    54615961 , -2518769

It seems this may be a regular bug at the moment but I was hoping to upgrade the nomination as the area is fairly sparse, so I was aiming to get a couple of nominations through the review process on a fairly quick turnaround.

Any advice?

Thanks

2

Basically the only way to fix this for your existing nomination is for Niantic to step in and fiddle with things.

1 Like
3

I was just able to put an In Queue submission on hold, so I don’t think tis is a wide spread issue. I was also able to release it from the hold.

The submission in question, when was it submitting? Are you able to provide a screenshot showing it’s still in queue and not in another status?

4

This is a not-infrequent issue with specific nominations.

5

Yes, so for the OP to say that it is happening to other right now is incorrect, as I haven’t seen any reports from others recently.

This is why I used my In Queue submission to see if it was a wide spread issue, and it doesn’t appear to be.

A screenshot from Contribution Management would still be helpful @GuitarMan147.

6

The op never said it affects everyone. They are correct that it is a regular issue though.

What is a screenshot going to show? That they aren’t lying about it being in queue? :roll_eyes:

7

You need to provide as much info as possible with any tech issue. You have been very unconstructive today, BTW.

8

No, you don’t. Setting ridiculous requirements is unhelpful.

9

I used to work customer service for online companies, and when someone reported an issue, we asked them to provide as much info as possible so we could pass it onto the correct department. Asking for more information is the best, and it’ll let Niantic staff know where to look. Simply as that.

10

Like I said, the more info provided, the better help that can be received. Again, I have experience with this. No need to get all bent out of shape because you think doing things this way is ridiculous, as it isn’t.

12

Can I remind everyone to remain respectful of each other.
I don’t see need for further comments.

1 Like
13

Here is a link to another thread where someone was experiencing the same issue: Submissions stuck in queue, unable to put back on hold or edit

I tried upgrading the nomination again and this has worked - I must have previously clicked “Upgrade Next” when I received the error message to say it was unable to upgrade the nomination. Hopefully having applied the upgrade, this will help avoid any issues with the nomination.

2 Likes
14

That post has similar info as I asked if you could provide, such as a screenshot showing the issue/error that you are getting. The staff most likely won’t move forward with this until you provide additional info, such as a screenshot showing the error you are receiving. Here, in this post, the OP from the other thread provided a screenshot, and Niantic staff later did look into it.

I also can say that Upgrade Next has caused issues like this in the past. I don’t use Upgrade Next, many due to ML approving the majority of my nomination within 24-48 hours, but also due to the known issues with editing with the option.

Again, can you please provide a screenshot of the error you are receiving? This will be extremely helpful to the staff when resolving this issue.

15

The original poster has helpfully updated to say that the issue seems to have been resolved.

16

Sorry, I think because the thread title only mentions wanting to put on hold and unable to edit that’s what I assumed was the issue. I see now upgrading was also the issue.

1 Like