Currently the Scratch site is somewhat unstable, with some pages not loading or showing the Whoops! error. Sometimes comments won't post unless you attempt them several times. This is an issue that multiple people have noticed.

However, among the most concerning are the fact that reporting something will sometimes fail. That's not a huge deal as if you know it failed you can simply try again. However, sometimes it may look as though the report has succeeded even if it has failed. And to make things even more complex, how to tell if it really worked or not depends on what you're reporting– a project, a comment, or something else. That's why I have created this topic, so that people can check.

Reporting Projects
Projects are the easiest, because if it says the report has successfully gone through, then it has– if it failed, you'll know that it failed. Reporting a project can fail either via in two ways: one of them will simply tell you that it has failed:


The other way is for the report box to simply hang forever. If it's been 5-10 seconds and the report still hasn't confirmed as having gone through, it's best to copy your report text, refresh the page and try again.

Sometimes, reporting a project can just continuously fail no matter how many times you try. If it doesn't work even after multiple attempts, you can always report it via the Contact Us page.

Reporting Comments (projects/studios)

Pay attention when reporting comments on projects and studios, because sometimes a dialog box saying the report worked may appear, even if it did not work. This confirmation looks like this:



The way to check if reporting a comment worked is to check if the comment turns pink. A comment that was successfully reported looks like this:



If the pink border does not show up around the comment within a few seconds, the report likely failed (even if a dialog box said it succeeded) and you should try again until the comment turns pink. Once the comment turns pink, it has been successfully reported.

Reporting Comments (profiles)

Comments on user profiles are similar to on projects or studios, the main difference being that the (somewhat misleading) dialog box after reporting does not show up. Instead, the dialog box simply closes and the comment may or may not turn pink. A successfully reported comment looks like this:



If it does not turn pink, just like with project or studio comments, try again until it does.

—-

These issues have been brought to the Scratch Team's attention, though they are already spending a lot of time working to make the site more stable in general, it is hoped they will make it more clear when a report has or has not worked, but in the meantime, I'm posting this information here to let everyone know– it ensures community safety, because if people think they have reported something when they haven't, this is obviously bad and can leave a lot of inappropriate content on the site, so I am putting this information out there.

Also, try not to report things that aren't inappropriate just to test this stuff out – all of the above examples were either reports that were made to fail, or legitimately inappropriate comments that I inspect-elemented to have my own name and text. Let's not make the Scratch Team's job any harder than it already is.

very informative!! congrats on the sticky ^^

Omg yes, thank you for this!

mrsrec wrote:

The other way is for the report box to simply hang forever. If it's been 5-10 seconds and the report still hasn't confirmed as having gone through, it's best to copy your report text, refresh the page and try again. Projects are the easiest, because if it says the report has successfully gone through, then it really has.

I refreshed the page and it's still hanging forever.

<0-0::sensing>//This is Charles; he protects my signature from evil kumquats.
when I'm spawned::events hat//This is the code Charles' brain runs on.
forever
if <[100] > (distance to [an evil kumquat v])> then
delete the evil kumquat::control
end
end

EDawg2011 wrote:

mrsrec wrote:

The other way is for the report box to simply hang forever. If it's been 5-10 seconds and the report still hasn't confirmed as having gone through, it's best to copy your report text, refresh the page and try again. Projects are the easiest, because if it says the report has successfully gone through, then it really has.

I refreshed the page and it's still hanging forever.

Yes, that's been happening to me as well. Unfortunately, I can only tell you if it worked or not, I can't make it work more often.

There's also been a bit of weirdness with reports not just on the technical side, but on the moderation side as well. Someone posted a project whose description was just “@mrsrec is stupid” and nothing else. I reported it but it wasn't removed. A few days later, just in case that report didn't work (since there's been instability on that in general as laid out in the OP) I wrote to Contact Us. And no answer. This problem may be a bit deeper than my OP shows. I am hoping a developer or someone can comment on the site issues in general– even though I'm sure they're already spending a lot of time working on just keeping the site up, keeping the community safe is just as important.

IT HAPPENED TO ME

I like how everything is worded so formatively.

GM15TOT wrote:

IT HAPPENED TO ME

What “happened” to you, exactly?

Excuse me, I have a problem with reporting. When I try to report some projects, it takes forever to load, but they never submit. What's going on? Honestly, I want to report some projects that sound like I could get harassed more, but surprisingly, they're not reporting. Why is sending reports slow?

bren319 wrote:

Excuse me, I have a problem with reporting. When I try to report some projects, it takes forever to load, but they never submit. What's going on? Honestly, I want to report some projects that sound like I could get harassed more, but surprisingly, they're not reporting. Why is sending reports slow?

Yeah, usually just report a few times, but for projects in particular it seems like sometimes they just may never go through even if you try like 15 times.In those cases you can use Contact Us but it's a bit slow.

On August 17th I reported a project to Contact Us whose description was “@mrsrec is stupid” (this was via Contact Us because reporting directly wasn't possible). Yesterday (August 23rd) I got back a response, and the project is now unshared.

However, Contact Us for every single inappropriate project is still not really a great long-term solution. I hope the developers have an update soon.

PaperMarioFan2024 wrote:

I like how everything is worded so formatively.

GM15TOT wrote:

IT HAPPENED TO ME

What “happened” for you, exactly?

That person literally posted here

{what method did you use::control hat
answer on profile ::motion
} ::operators

Ooooh no wonder why my report won't go through ;-;

medians wrote:

That person literally posted here

But it still doesn't answer my question:

PaperMarioFan2024 wrote:

#4 What “happened” to you, exactly?

Unless maybe I misunderstood and they probably didn't read the OP or something.

I've figured the issue out.
Note that this was a legitimate report for tagspamming so false reporting isn't much of an issue here.

This seems to *still* be happening occasionally! It is happening a lot less often, but sometimes project reports are not going through.