Error Codes

A UES or Unscheduled Error Screen is a function that can abruptly stop all ScriptOS functions and do what is known as a "hard restart" when all elements stop rendering and the UES screen pops up. The UES screen usually says something like this:

"A critical system component of ScriptOS has failed. ScriptOS will restart shortly."
"ERROR_CODE: [error code]"

The UES screen has both visual and audible confirmation of an error. The audible form sounds like a repeating siren.

This page has all of the error codes and what they each mean. We have provided a table of contents to make your search easier.

First off, if you couldn't tell before, ScriptOS is still is the very early stages of release, therefore you are running developer betas, which could be unstable. Second, ScriptOS uses experimental methods to do things that were never done before, like Low Frame Rendering & Render Request Limit(s). And last but not least, the UES screen allows you to keep using ScriptOS without closing and reopening the window or tab. So, that is why a UES screen could occur.

This error occurs when the clone manager of ScriptOS has encountered a critical error. If the reboot does not fix the error, it will result in a bootloop. In a future update, the clone manager will be shutdown to prevent a bootloop. This error can happen at anytime, and is currently not able to be predictable. 

Since ScriptOS 15 (1.1.1.7.x), the clone manager has been disabled due to some incompatibility with the Precision Render 2.x new feature, called Low Frame Rendering. The Clone Manager will be enabled in a future update that is compatible with the latest version of the Precision Render.

This is when the Active Frame Reputation (AFR; average framerate) is too low for ScriptOS to run. This error will only occur if the deep sleeping function is off, and the frame rate is under 0.75 for at least 1.5 seconds. This error may also occur if your browser or application running ScriptOS (like Scratch or TurboWarp) stops responding.

This error occurs when the element render has been interrupted; either it stops rendering for an extended period of time (RENDER_CYCLE_INTERRUPTED), or the script unexpectedly stops and then runs again (RENDER_PROCESS INTERRUPTED).

The RENDER_CYCLE_INTERRUPTED error can cause a boot loop, but the RENDER_PROCESS_INTERRUPTED should not cause a boot loop, since the error is derived from an unexpected stop and resumption of the rendering script. This error can also occur when the render has entered a "Deep Sleep" mode, in which the render forcefully stops itself from rendering for some frames and then resumes rendering.

Since ScriptOS 15 (1.1.1.7.x), this error cannot be user-triggered. An internal error has to have occurred to experience this error.

The VVID_INVALID_OUTDATED_OS error occurs when the OS detects that it is outdated by a minimum of 3 major revisions (example: 1.1.1.7.5; 7 is the major revision) or 8 minor revisions (example: 1.1.1.7.5; 5 is the minor revision).

The VVID_INVALID_UNREGISTERED_V_OS error occurs when a version of ScriptOS doesn't line up with all of the registered versions. 

The VVID_INVALID_V_HASH error occurs when the current version of ScriptOS doesn't match the expected checksum or hash of the registered version.

While these errors are extremely rare, these are put in place to prevent any replications or leaked versions of ScriptOS to be able to run. These errors could occur at any time.

This error occurs when the TPA (Trusted Platform Authorization) System detects an invalid username checksum, therefore preventing unauthorized access to ScriptOS. This error only occurs upon bootup.

These errors occur when the render detected a costume that doesn't exist (RENDER_COSTUME_INVALID).

The RENDER_COSTUME_INVALID_UNICODE error occurs when an element (such as a logo or wallpaper) was called and the render detects that the costume doesn't exist. Since rendering an element such as a wallpaper or logo cannot be integrated into the Dynamic UI 3 Render Font Layout, it is required to use a different rendering system, which is why a different error code is needed.

The RENDER_COSTUME_INVALID_COSTUME error occurs when render detects a costume that doesn't exist and has more info to give about the error.  When the UES screen appears, the error code usually looks like this:

"ERROR_CODE: RENDER_COSTUME_INVALID_COSTUME (...)"

Anything that is in the brackets was the string that was attempted to be rendered.

The error code only occurs when a script has been called when it is not supposed to be, which has only been found to occur upon bootup.  As the name states, this error is very difficult if not impossible to troubleshoot.

This error occurs when the TurboWarp System Compliance (TSC) sub-system component fails to run or the system compliance check operation doesn't fully meet the minimum requirements.

This is a more general error code, and occurs when a system component fails.

This is when scriptOS attempts to contact a sub-system component and/or external system component (like cloudOS) but fails. This error code will only occur if the system environment is capable of running such a task (i.e if you are connected to internet, but cloudOS contact fails) and won't trigger a UES when the system environment isn't suitable (i.e you aren't connected to the internet).

This error occurs when a unifiedKey (either it be activeKey or tokenKey) attempts to validate a code, but the code doesn't match the Device ID that it is running on. 

This error should only happen if a specific scriptOS build in launched on a device that is not similar to the device it was registered on. This error should never happen if the code was generated on the device it is running on.

This error occurs when a unifiedKey (either it be activeKey or tokenKey) attempts to validate a code, but the validation process either fails or the code is validated, but it doesn't match the expected output.

This error can occur if the activeKey/tokenKey validated encounters an issue or is bugged.

This error only occurs when a unifiedKey (tokenKey) validates a code, but it doesn't match the expected outcome.

The reason this error is different from other errors is because this is meant for low-level code validation and execution (like VVID, secure code running, etc.). Higher level executions would attempt this process up to 3 times before it calls an error, but because low-level code is much more high-risk, there is only 1 attempt.