Users across multiple Discourse versions (2.9.0beta14, 3.1.0.beta2, and SaaS) reported encountering the error message “An error occurred: The requested URL or resource could not be found” when deleting spam users via the moderation queue. Despite the error, the user is successfully deleted — suggesting the issue is a misleading UI modal rather than a functional failure. JammyDodger confirmed the bug occurs when deleting users flagged for typing too fast, and noted that the error arises because the flag’s page no longer exists after deletion. The issue was linked to missing retention of typing-speed flags in the Review Queue history. A fix was implemented in PR #22501, and LordSimal confirmed the error no longer occurs post-fix. The bug affected both self-hosted and SaaS instances, and users noted it could occur even with a single post. JammyDodger reassigned the report to a related bug thread and confirmed a developer was assigned, with the fix now deployed.
When I tried to delete a new user who’d posted a load of foreign-language spam I got this message. I’m on 2.9.0beta14. It was the same whichever of the two “delete” options I chose.
Edit: Just noticed that the user did get deleted (“Deleted via review queue”) so maybe I just clicked the button too many times.
Sorry for the delay, I meant to reply to this one at the time, but for some reason did not get round to posting the draft…
I also see this a fair bit when deleting spam users. Everything works as expected, but you do get the “An error occurred…” modal pop up, which can be misleading.
To replicate:
Sign up test user
Paste a chunk of Lorem Ipsum in for their first post to trigger 'New user typed their first post suspiciously fast, suspected bot or spammer behavior.`
When reviewing, select ‘delete user’
Receive error modal (though everything has worked and the user has been deleted)
I think your report is more similar to this Contribute > Bug so I’ve slipped your post across.
We think it’s connected to the ‘typing too fast’ flags not being retained in the Review Queue history, and when following the individual notification from the menu you land on a specific page for that flag. When deleted, the page no longer exists which then throws up that info box.
Someone has been assigned to investigate, and I think a fix is in the pipeline.