1

Patrolling Recent Changes is not working. “An error has occurred”. I am using Google Chrome Web Browser, and I’m not sure what’s up with the tool. It’s leaving me a message about having an error. Noted 4/8/2017

1260×820 256 KB
2

Anything you can do to help?

3

FYI: I did suggest that @Leafdapple09 try skipping the first edit, but they were unable to do so and said “When I click skip the page does not reload or move me onto something else. It stays at the same thing.”

I also suggested clearing their cache, cookies, closing the browser, and relaunching, but no luck there either. As a last ditch effort I also suggested trying a different browser, but I’m not sure they had a chance to try doing that. 

4

Thanks for the report, @Leafdapple09 , and the troubleshooting, @Eric ! Usually when this error comes up, it’s because there’s some kind of RC one-off that the RCP tool can’t handle - like, a page has been moved without a redirect, or deleted, while it was loaded into the RCP tool (or pre-loaded, since the edits load up a couple at a time). It’s sort of like an edit clash. That doesn’t usually persist after reloading the tool, though.

At other times, some other kind of “bad data” can make an edit stick, too. That’s typically handled okay if it’s patrolled manually through the RC list instead; we just have to get it out of the queue for the tool to run smoothly for all, again. (For anyone looking to solve an issue like this, it’s typically either the edit that’s up in the tool at the time, or the next one in the queue, so clearing out a few edits through Traditional RC in that time frame often does the trick.) 

In this case, it looks like you’ve been patrolling since this report, @Leafdapple09 ? Is it working for you again now? Perhaps the bad edit has already been zapped in the time since:slight_smile:

5

Great. Thanks for the info, @Anna ! 

I did confirm via talk page that RC Patrol is working again for  @Leafdapple09 .:slight_smile:

6

Ah, good to hear - thanks for the follow-up, Eric!