> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/es/comandos-de-powershell/new-uderrorboundary.md).

# New-UDErrorBoundary

New-UDErrorBoundary envuelve una sección de código de PowerShell Universal para que los errores de tiempo de ejecución se capturen y se muestren en la página en lugar de bloquearla.

### Sinopsis

Define un nuevo límite de error alrededor de una sección de código.

### Sintaxis

```powershell
New-UDErrorBoundary [-Content] <ScriptBlock> [<CommonParameters>]
```

### Descripción

Define un nuevo límite de error alrededor de una sección de código. Los límites de error se utilizan para capturar errores y mostrarlos en la página.

### Parámetros

#### -Content

El contenido que se va a capturar en un límite de error.

```
Required?                    true
Position?                    1
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### Parámetros comunes

Este cmdlet admite los parámetros comunes: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable y OutVariable. Para más información, consulte [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Salidas

### Ejemplos

#### Ejemplo 1: límite de error

```powershell
New-UDErrorBoundary -Content {
   throw 'This is an error'
}
```

Define un límite de error que captura la excepción que se lanza y la muestra en la página.

\[Component("Error Boundary", "Bug", "Creates a new card.")]


---

# 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.devolutions.net/powershell-universal/es/comandos-de-powershell/new-uderrorboundary.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.