One excessive downtime event
caddis_get_equipment_excessive_downtimeFetch an excessive downtime record for a piece of equipment, including operator-assigned reason, by providing shift history and status log IDs. Returns TOON-encoded data.
Instructions
Fetch a single excessive downtime record (with operator-assigned reason, if any) identified by the shift history + status log pair for a piece of equipment.
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 |
|---|---|---|---|
| equipId | Yes | Numeric identifier (accepts either string or number form) | |
| statusLogId | Yes | Status log ID for the event | |
| shiftHistoryId | Yes | Shift history ID for the event |