Exit Codes#
See also
For a full list of exit actions, see Exit Actions.
The following is a list of possible task exit codes and their descriptions. Users should handle user exit codes.
User exit codes are the exit codes returned by the user’s task.
Preflight exit codes are the exit codes returned by the preflight tests.
OSMO configuration exit codes are the exit codes returned by the OSMO when handling data inputs/outputs and communicating with the service.
Infra exit codes are the exit codes returned by the service when processing the user task.
Note
If a task encounters multiple exit codes, the highest exit code will be selected.
Exit Code |
Description |
|---|---|
0 |
Task completed. |
1-255 |
User failure. 137 Error Code explanation. |
256-257 |
OSMO initialization failure. |
Exit Code |
Description |
|---|---|
2002 |
Unknown runtime error. |
2010 |
Download operation failed. |
2011 |
Mount operation failed. |
2012 |
Upload operation failed. |
2020 |
Invalid authentication token for connecting to the service. |
2021 |
Service connection timed out. |
2022 |
Failed to send/receive messages to/from the service. |
2023 |
Failed to send/receive messages to/from the user task. |
2024 |
Barrier synchronization failed. |
2025 |
Failed to create or process metrics. |
2030-2040 |
Miscellaneous failure. |
3000 |
Upstream tasks failed. |
3001 |
Backend error. |
3002 |
OSMO server error. |
3003 |
Start error. Task failed to start execution. |
3004 |
Evicted. Task was evicted from the node. |
3005 |
Start timeout. Task took too long to initialize. This may happen if the task gets stuck pulling secrets or images. |
3006 |
Preempted. The task was preempted to make space for a higher priority task. |
4000 |
Unknown error. |