- Sphere Engine overview
- Compilers
- Overview
- API
- Widgets
- Resources
- Problems
- Overview
- API
- Widgets
- Handbook
- Resources
- Containers
- Overview
- Glossary
- API
- Workspaces
- Handbook
- Resources
- RESOURCES
- Programming languages
- Modules comparison
- Webhooks
- Infrastructure management
- API changelog
- FAQ
The status code of the scenario execution summarizes its outcome. The codes that Sphere Engine uses for labeling
executions are unified all over the module components. This consistent convention is used for API submissions,
workspaces JavaScript SDK events, webhook messages, partial execution results, etc.
Note: Values of the status codes are unified also across Sphere Engine modules. In this case, the meaning of some
values can have slightly different meanings (e.g., "success" vs "correct", "compilation error" vs "build error"). Some
values may also not being present. These minor differences are always in line with differences between modules.
The following two tables present available values of the status code.
List of transient execution states
| Status | Name | Description |
|---|---|---|
| 0 | waiting | waiting in the queue |
| 1 | preparation | the environment for the execution is being prepared |
| 3 | execution | execution in progress |
List of final execution states
| Status | Name | Description |
|---|---|---|
| 11 | build error | the execution failed during the build stage |
| 12 | runtime error | an error occurred during the execution (e.g., division by zero) |
| 13 | time limit exceeded | the execution exceeded the time limit |
| 14 | fail | the execution was considered unsuccessful during evaluation stage |
| 15 | ok | the execution was successful |
| 20 | internal error | an unexpected error occurred on the Sphere Engine's side; try to re-run; please contact us if the error persists |
| 22 | project error | the execution failed due to an error in the project configuration; refer to debug_log for more information |