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

# Error handling

## Global Error Handler

Set a global error handler on `YieldProvider` to catch errors from all action hooks:

```tsx
<YieldProvider onError={(error) => {
  // Log to your error tracking service
  Sentry.captureException(error)
  toast.error(error.message)
}}>
  {children}
</YieldProvider>
```

## Per-Hook Error Handling

Each action hook (`useDeposit`, `useRedeem`, `useApprove`) accepts local `onError` callbacks:

```tsx
const { deposit, error } = useDeposit({
  vault: 'yoETH',
  onError: (err) => {
    toast.error(`Deposit failed: ${err.message}`)
  },
})
```

Both the local and global handlers are called when an error occurs.

## Error States in Read Hooks

Read hooks expose `isError` and `error` fields:

```tsx
const { vault, isError, error } = useVault('yoETH')

if (isError) {
  return <div>Failed to load vault: {error?.message}</div>
}
```

## API Errors

The `ApiClient` throws `ApiError` with an HTTP status code:

```ts
import { ApiError } from '@yo-protocol/core'

try {
  const snapshot = await client.getVaultSnapshot(address)
} catch (err) {
  if (err instanceof ApiError) {
    if (err.statusCode === 404) {
      // Vault not found
    } else if (err.statusCode >= 500) {
      // Server error — retry
    }
  }
}
```

## Common Errors

| Error                      | Cause                                   | Solution                                         |
| -------------------------- | --------------------------------------- | ------------------------------------------------ |
| "Client not available"     | Hook used before providers are ready    | Ensure `YieldProvider` is inside `WagmiProvider` |
| "Account not connected"    | Action called without wallet connection | Check `useAccount()` before calling actions      |
| "WalletClient is required" | Core client used for tx without wallet  | Call `client.setWalletClient()` first            |
| User rejected transaction  | User declined in wallet                 | Catch and show appropriate UI                    |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.yo.xyz/integrations/integration-guides/sdk/guides/error-handling.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.