(Redirected from Error (2.0))
- This article is about errors in Scratch 3.0. For other uses, see Error (disambiguation).
An error is a mistake or a malfunction that occurs when a program runs into a problem or behaves incorrectly and cannot complete the instructions it is given.
In Scratch 3.0, an error can occur when the project crashes, has failed to load, is used with incompatible hardware or software, runs into a script error, or is overloaded and cannot handle the project it is currently running. There are also many errors to do with the Scratch Website, and there are many types of errors that can occur.
Project Crash
- Main article: Making Scratch Crash
When variables and lists get too long, there are too many clones, or the project is doing too many things at once, it may crash. In other cases, an error will be always shown when trying to access it.
The screen is usually blue, has a "reload" icon, and says "Oops! Something went wrong. We are so sorry, but it looks like Scratch has crashed. This bug has been automatically reported to the Scratch Team. Please refresh your page to try again." The text was gray on early versions of the 3.0 online editor before being changed to white.
There is a white button that lets the user reload the page to try loading the project again. It can be shown on both the project and the editor.
Additionaly, there are two variants; one used in April Fools 2025, and one used for the 7th day of Scratchtober 2025, where it shows a message in the same style that "this project was glitched". [1]
Error Code
Scratch previously used Sentry to collect errors automatically. When Sentry sent the detail to the Scratch Team privately, an error code was generated and added to the bottom of the error message, for example, "Your error was logged with id 81df2c5a235e853adbf8375dd094b6a8". This changes each time the error was reported, and the ID itself did not give any information without data sent to Sentry. Later, Scratch stopped using Sentry, and its code was removed from the error message. [2]
Error Details
Some browsers have a feature to see the logs from JavaScript.
- On Chrome and Firefox, press F12 and see Console.
- On Mac, ⌘ Cmd+⌥ Option+I will work.
Paint Editor Crash
Whenever a broken SVG file is uploaded, the paint editor may break, but the rest of the Scratch program can still be used.
Loading Error
Sometimes, a project may fail to load, and this can cause a crash. In other times, the project can either be broken or overloaded.
In 2.0, there was a dialog saying "The project failed to load and the Scratch Team has been notified." with an "OK" button.
When Scratch 3.0 was released, there was a bug that caused projects to fail to load and crash instead. This was eventually fixed a few days later.[citation needed]
Scratch Lab
When a Scratch Lab project with experimental extensions is loaded into the normal Scratch editor, it may fail to load and will break.
Incompatible Software or Hardware
- Main article: System Requirements
Old operating systems, unsupported browsers (such as Internet Explorer, Opera, and older versions of Chrome, among others), or minimum system requirements on computers (including WebGL) can cause errors because they are incapable of running Scratch 3.0. If incompatible software or hardware cannot run Scratch 3.0, users should try using older versions instead (such as Scratch 2.0 or Scratch 1.x).
This error may also happen on lower-end devices, like Chromebooks, even if a user is using a supported browser and device.[3] This problem is usually fixed by waiting it out, restarting, or hardware restarting.
Script Errors
- Main article: Script Error
Scripts can sometimes be made to do impossible things, like dividing by zero or changing the sprite position to a string. When this happens, a script error occurs. Unlike most other errors, they simply skip the block with the error and continue on.
Website (HTTP) Errors
Errors might occur while using and viewing the Scratch Website. They are shown below by their HTTP status codes.
403
- Main article: 403 Error
The 403 error occurs when a page requested is forbidden, such as when an account with an unverified email tries creating a new post on the Scratch Discussion forums.
The test page for the error is viewable here.
404
- Main article: 404 Error
The 404 error occurs when the page that was requested does not exist. The layout uses the Scratch 2.0 layout when viewing deleted users and studios, and uses the Scratch 3.0 for viewing deleted projects.
The test page for the error is viewable here.
The downloads.scratch.mit.edu page contains another version of the 404 error.
429
| Please expand this article or section. You can help by adding more information if you are an editor. More information might be found in a section of the talk page. (January 2023) |
The 429 error occurs when actions or requests are performed too frequently. An example is moving around the website too quickly. The error page contains an embed of the project "DINO-GIFFIC!!!" by former Scratch Team member raimondious.
The test page for the error is viewable here.
429-email
This variant of the 429 error occurs when too much mail was sent too frequently, usually through excess Help Center messages that send emails to the Scratch Team.[citation needed] The page contains an embed of the project "Evil Mailbox remix" by the same user.
The test page for the error is viewable here.
500
- Main article: 500 Error
The 500 error occurs when an internal error occurs, such as the server not responding, the server being overloaded, or the Scratch Team doing tests without Maintenance Mode.
The test page for the error is viewable here.
503
- Main article: Maintenance Mode
HTTP 503 (Service Unavailable) is the status code for Maintenance Mode when the Scratch Team is making changes to the website.
The test page for the error is viewable here.
Forum Error Page
The forums have their own special error page that appears when the forums are down separately from the website itself. This page contains an embed of Scratch's Twitter (now known as X) account; this no longer shows a live feed of updates as Twitter's logged-out feed now orders tweets by the number of likes.
References
- ↑ projects:1226957650
- ↑ cwillisf. (2023-01-27). "We're no longer planning to use Sentry in this way." https://github.com/scratchfoundation/scratch-gui/pull/8751
- ↑ topic:376973