> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemo/relay/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemo/relay/_mcp/server.

# Struct PopScope Params

> Builder parameters for `pop_scope`.

Generated from `cargo doc --no-deps -p nemo-relay -p nemo-relay-adaptive -p nemo-relay-pii-redaction -p nemo-relay-ffi -p nemo-relay-types -p nemo-relay-plugin -p nemo-relay-worker-proto -p nemo-relay-worker`.

<pre />

Builder parameters for [`pop_scope`](/reference/api/rust-library-reference/nemo-relay/api/scope/fn-pop-scope).

## Fields

### `handle_uuid: &'a Uuid`

UUID of the scope that should be popped.

### `output: Option<Json>`

Optional JSON payload exported as the semantic scope output.

### `metadata: Option<Json>`

Optional JSON payload metadata to be appended to the metadata set when the scope was created.

### `timestamp: Option<DateTime<Utc>>`

Optional timestamp recorded on the emitted end event. When omitted, the runtime records the current UTC time, or one microsecond after the handle start time if the current time is not later.

## Implementations

### `impl<'a> PopScopeParams<'a>`

<pre />

#### `builder`

<pre />

Create a builder for building `PopScopeParams`. On the builder, call `.handle_uuid(...)`, `.output(...)`(optional), `.metadata(...)`(optional), `.timestamp(...)`(optional) to set the values of the fields. Finally, call `.build()` to create the instance of `PopScopeParams`.