> For the complete documentation index, see [llms.txt](https://docs.orbs.network/v2-contract-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.orbs.network/v2-contract-sdk/orbs-contracts/error-handling.md).

# Error handling

The execution flow of Orbs contracts does not include error handling, meaning that once an error occurs, code execution stops, the state in the blockchain is not stored, and any changes done up until the error are reverted.

When the contract execution hits an error, the `ExecutionResult` is set to `ERROR_SMART_CONTRACT`, and an error message is set in `OutputArguments`.

Using `panic` is the simplest way to report an error from within a contract, and in a similar way seen above, the error message is returned as part of the output arguments of the execution.

For example, the code:

```go
func throw() {
    panic("the error message from the code")
}
```

Will output the following result on execution:

```javascript
{
  "RequestStatus": "COMPLETED",
  "ExecutionResult": "ERROR_SMART_CONTRACT",
  "OutputArguments": [
    {
      "Type": "string",
      "Value": "the error message from the code"
    }
  ]
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.orbs.network/v2-contract-sdk/orbs-contracts/error-handling.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.