Skip to main content
A workflow defines what to collect and when. Each execution is a run. Kadoa tracks workflow, run, Assistant, and support states separately.

States

These diagrams show the common transitions.

Workflow

Active workflows run once, on a schedule, or continuously. An active workflow can be waiting between runs.

Run

Kadoa combines data quality checks with agent review. Runs that meet the approval requirements pass automatically. Unresolved issues or required human checks go to a Kadoa reviewer before delivery. Previous results stay visible.

Assistant activity

When the Assistant needs input, it is idle and shows Reply needed. Repairs appear as Updating in the UI.

Support

Support is independent of the other states. An open case does not mean a repair is running.

UI states

Badges show each state separately. For example, Preview + Updating + In support means a preview is being updated and a support case is open. Previous data stays visible during updates and after failures. The banner explains the current activity or action needed.

API states

Use presentation to display states and availableActions to enable controls. List and detail responses include: A preview being updated returns:
The API rechecks permissions and state when you submit an action. Outdated batch Assistant previews block approval with reason PREVIEW_OUT_OF_DATE. Approval requests return HTTP 409 until Kadoa refreshes the preview.

Filtering workflows

Filter by dashboard group, displayState, or lifecycle state:
Groups are attention, working, support, failed, active, complete, and paused. Open support cases always place workflows in support. You cannot filter by presentation.status.