Retained results

Capture a retained output prefix

Explicitly freeze observed background output into a new immutable result. Retrying creates another result; it never executes the command. No automatic capture, Activities record, listing or idempotency key. Accepts an application/json object (including {}) of at most 4096 bytes. The total capture deadline is 60000 milliseconds. Capture starts at independent zero offsets, stops each stream at observed EOF or its requested cap, and stores the wrapper diagnostic once. This is a finite prefix from mutable guest paths, not an atomic snapshot or completion proof. Expiry is measured from capture_started_at. No query parameters or arbitrary metadata are accepted. A lost response may leave a committed result until expiry. Responses are no-store; Location is the relative metadata URL.

Requires the member role or higher.

post/computers/{id}/executions/{executionId}/retained-output

Request

  • Base URL: https://app.mandala.computer/api/v1
  • URL: https://app.mandala.computer/api/v1/computers/{id}/executions/{executionId}/retained-output
  • Auth: HTTP bearer

Path parameters

idstring required

The computer id.

executionIdstring required

The opaque execution_id from a backgrounded exec (exec_ followed by 32 lowercase hex characters).

Request body

max_bytes_per_streaminteger
retention_secondsinteger

Response

Published immutable metadata, never raw output. The original execution remains a separate volatile handle.

version1 required
result_idstring required
kind'background-output' required
state'ready' required

Bytes were published, not a statement of task success.

account_idstring required
computer_idstring required
workspace_idstring nullable required
execution_idstring required
capture_started_atstring date-time required
captured_atstring date-time required
expires_atstring date-time required
source'volatile_guest_files' required

Changes

No recorded changes to this operation across all 1 revision of this API.