Skip to content
Proud to collaborate with Microsoft for Startups

data.chat.engine.runs.list ​

Paginated list of workflow-engine runs for the caller's org

Paginated list of workflow-engine runs scoped to a (org, user) pair.

Reads the engine's own workflow_states table — one entry per workflow run, derived from the latest state row per workflow_id. started_at is the first row's created_at and ended_at is the latest row's created_at when terminal.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-chat
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
organization_uuiduuidYes—Organization UUID — scopes runs to org-owned rows
user_uuiduuidYes—User UUID — auth check (not a row filter)
projectstringNo—Optional project slug, e.g. 'ltinteg-api-core'
workflow_typestringNo—Exact workflow_type match; takes precedence over prefix
workflow_type_prefixstringNo—Prefix match on workflow_type, e.g. 'agents.'
statusstringNo—One of pending
sincestringNo—ISO 8601 lower bound on started_at
untilstringNo—ISO 8601 upper bound on started_at
actor_uuiduuidNo—Optional actor UUID filter (matches WorkflowState.actor)
cursorstringNo—Opaque pagination cursor from a previous page
limitintegerNo25Page size (1..100, default 25)

Output Schema ​

FieldTypeRequiredDefaultDescription
runslistYes—Engine run dicts sorted by started_at DESC
next_cursorstringNo—Cursor for the next page, or null when exhausted
summarydictYes—{total, by_status:{pending,running,completed,failed}}
errorstringNo—Error message when query failed
error_typestringNo—Error class name when query failed

States ​

StateInitialTerminalSuccessAuto-advanceDescription
doneYesYesYes——

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "data.chat.engine.runs.list",
  "initial_data": {
    "organization_uuid": "value",
    "user_uuid": "value"
  }
}