Read or tail a setup run's log
Returns the run’s output after a cursor: stdout and stderr as the script produced them, marker lines naming each script line before it runs, and system lines for the setup phases around the script (provision, gpu_check, profile, cleanup). Secrets are redacted before storage. To tail a live run, loop with cursor=nextAfter and waitSeconds=0, sleeping two seconds client-side, until status is terminal and a page comes back empty.
Authorizations
A Recursion API key, created in the console under API keys.
Headers
Optional tenant consistency check. When present, it must name the tenant bound to the API key, including when x-organization-id is default.
1Organization in which to act. Required for a tenant-scoped API key. Optional for an organization-scoped key, where it must name that same organization. The value may be an organization id or default.
1Path Parameters
Environment id (UUID).
Setup run id (UUID).
Query Parameters
Sequence cursor from the previous log page; omit to start at the beginning.
Maximum lines to return.
1 <= x <= 2000Block up to this many seconds for more lines, capped at five seconds.
0 <= x <= 60Response
OK
Log lines after the requested cursor, in order.
Cursor to pass as cursor on the next call.
-9007199254740991 <= x <= 9007199254740991Run status when the page was read.
Whether the run exceeded the retained log size.