Production cycles for a run
caddis_get_run_cyclesRetrieve all production cycles for a specific run. Provide the run ID to get data in TOON format.
Instructions
All production cycles associated with a specific run. Use this instead of caddis_get_equipment_cycles when the scope is a known run.
Responses are TOON-encoded (toonformat.dev) — a token-efficient JSON dialect mixing YAML-style indentation with CSV-style tables. Example:
name: Caddis Co timezone: America/Denver equipment[3]{id,name,tags,current_status.status,current_status.reason_id}: 1,Mill A,"["cnc","critical"]",running,null 2,"Press, Big",null,down,3 3,Lathe C,null,null,null
Object fields:
key: value; nested objects indent their children.Uniform arrays of objects:
field[N]{cols}:followed by N indented comma-separated rows in column order.Nested objects inside table rows are recursively flattened to dotted columns (e.g.
current_status.status,input_setup.cycle.logic); a null parent yieldsnullacross all its dotted columns (see row 3 above).Primitive arrays at object level:
field[N]: a,b,cinline.Arrays inside table cells are JSON-stringified into a single cell value (
JSON.parse()to recover); empty arrays render asnull(see rows 1–3tagscolumn).Strings with commas/colons/quotes/leading whitespace are double-quoted (escapes:
\\,\"); other strings, numbers, booleans, andnullare bare.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| runId | Yes | Numeric identifier (accepts either string or number form) |