Skip to main content
DELETE
JavaScript
Unwire a memory layer from one variation. Objectives that variation runs from now on no longer see the layer’s entries.
The id is the assignment’s avml_... value, from the attach response or the variation’s info.memoryLayerAssignments, not the layer’s id.

The layer survives

This deletes the assignment, the join between the variation and the layer, not the layer. The memory layer and its entries stay in the workspace, ready to attach to another variation. Removing the assignment cleanly frees the layer, so a layer that is no longer assigned anywhere is deletable right away, no orphaned assignment left holding it. Objectives already running are unaffected: each froze its cascade into a configSnapshot at creation, so detaching a layer changes future runs, not one in flight.

Attach a memory layer

Wire a layer back onto a variation.

Reposition a memory layer

Move it in the cascade instead of removing it.

Delete a memory layer

Remove the layer itself, once nothing assigns it.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

workspaceId
string
required

Workspace ID.

Example:

"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"

agentId
string
required

Agent ID. Accepts the canonical agent_… form or the external_id:<value> form.

Example:

"agent_01HXKD2E5NQM3T9AYWCFMGWT9Y"

variationId
string
required

Variation ID. Accepts the canonical agentvar_… form or the external_id:<value> form.

Example:

"agentvar_01HXKD2E5NQM3T9AYWCF32BSPP"

id
string
required
Example:

"avml_01HXKD2E5NQM3T9AYWCFX8AF59"

Response