Answer: A run reports one of five statuses: running, paused, completed, failed, and aborted, with paused covering three situations (needs input, at a boundary, iteration cap). Running means Kiro is executing or scheduling nodes; completed means every required top-level node completed; failed means a node failed and the failure propagated to the run; aborted means the run was stopped or a repeat used onMaxIterations: "abort". Status: Confirmed Entry: tool/kiro/agents-and-automation/workflow-run-statuses Revision: 3 Digest: sha256:48d59558692c7270 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:46:58Z Last changed: 2026-11-18T13:28:43Z (aborted: — → The run was stopped, or a repeat used onMaxIterations: "abort") Last verified: 2026-11-20T13:34:32Z Next check: 2026-11-21T13:34:32Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of number of statuses | five | [1] | 2026-11-20 running | Kiro is executing or scheduling nodes | [1] | 2026-11-20 paused situations | three | [1] | 2026-11-20 completed | Every required top-level node completed | [1] | 2026-11-20 failed | A node failed and the failure propagated to the run | [1] | 2026-11-20 aborted | The run was stopped, or a repeat used onMaxIterations: "abort" | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Run and manage workflows - Workflows - Features - Docs - Kiro". https://kiro.dev/docs/workflows/manage/ Role: primary. Accessed: 2026-11-20T13:34:32Z Quote: "A run reports one of five statuses" (Supports: number of statuses) Quote: "running Kiro is executing or scheduling nodes" (Supports: running) Quote: "paused covers three different situations" (Supports: paused situations) Quote: "completed Every required top-level node completed" (Supports: completed) Quote: "failed A node failed and the failure propagated to the run" (Supports: failed) Quote: "aborted The run was stopped, or a repeat used onMaxIterations: "abort"" (Supports: aborted) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 976bf62dae28cb2f00c38b078a4304c7fff085ada5242c5a8e90e2965e6af7dc (captured 2026-11-20T13:34:32Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:34:32Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:34:32Z Last attempt: 2026-11-20T13:34:32Z Notes and limitations: Extracted automatically from a single official source (section "Understand run status"). Related: https://latestn.com/tool/kiro/agents-and-automation/write-scheduled-task-prompt How do I write the prompt for a Kiro scheduled task? https://latestn.com/tool/kiro/commands-and-shortcuts/available-slash-commands What slash commands are available in Kiro's IDE chat? https://latestn.com/tool/kiro/commands-and-shortcuts/chat-tabs-debugging-shortcuts What keyboard shortcuts does Kiro have for chat, tabs, and debugging? https://latestn.com/tool/kiro/agents-and-automation/when-to-use-a-bot When should I use a Kiro bot instead of another Kiro Crew option? https://latestn.com/tool/kiro/agents-and-automation/when-to-use-workflow When should I use a workflow in Kiro Crew instead of a subagent? https://latestn.com/tool/kiro/agents-and-automation/workflow-patterns-overview What workflow patterns does Kiro support for common development tasks? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:28:43Z | changed | aborted: — → The run was stopped, or a repeat used onMaxIterations: "abort" | [1] 2026-11-18T13:28:43Z | changed | failed: — → A node failed and the failure propagated to the run | [1] 2026-11-18T13:28:43Z | changed | completed: — → Every required top-level node completed | [1] 2026-11-18T13:28:43Z | changed | running: — → Kiro is executing or scheduling nodes | [1] 2026-11-18T13:28:43Z | changed | failed status meaning: A node failed and the failure propagated to the run → — | [1] 2026-11-18T13:28:43Z | changed | completed status meaning: Every required top-level node completed → — | [1] 2026-11-18T13:28:43Z | changed | paused · iteration cap meaning: A repeat reached maxIterations with onMaxIterations: "pause" → — | [1] 2026-11-18T13:28:43Z | changed | paused · at a boundary meaning: A requested pause took effect at a safe node boundary → — | [1] 2026-11-18T13:28:43Z | changed | paused · needs input meaning: A step called send_message with severity warning and is waiting for you → — | [1] 2026-11-18T13:28:43Z | changed | running status meaning: Kiro is executing or scheduling nodes → — | [1] 2026-11-13T13:18:46Z | changed | failed status meaning: — → A node failed and the failure propagated to the run | [1] 2026-11-13T13:18:46Z | changed | completed status meaning: — → Every required top-level node completed | [1] 2026-11-13T13:18:46Z | changed | paused · iteration cap meaning: — → A repeat reached maxIterations with onMaxIterations: "pause" | [1] 2026-11-13T13:18:46Z | changed | paused · at a boundary meaning: — → A requested pause took effect at a safe node boundary | [1] 2026-11-13T13:18:46Z | changed | paused · needs input meaning: — → A step called send_message with severity warning and is waiting for you | [1] 2026-11-13T13:18:46Z | changed | paused situations: — → three | [1] 2026-11-13T13:18:46Z | changed | running status meaning: — → Kiro is executing or scheduling nodes | [1] 2026-11-13T13:18:46Z | changed | paused iteration cap: A repeat reached maxIterations with onMaxIterations: "pause" → — | [1] 2026-11-13T13:18:46Z | changed | paused needs input: A step called send_message with severity warning and is waiting for you → — | [1] 2026-11-13T13:18:46Z | changed | aborted status: The run was stopped, or a repeat used onMaxIterations: "abort" → — | [1] 2026-11-13T13:18:46Z | changed | failed status: A node failed and the failure propagated to the run → — | [1] 2026-11-13T13:18:46Z | changed | completed status: Every required top-level node completed → — | [1] 2026-11-13T13:18:46Z | changed | paused statuses: paused covers three different situations → — | [1] 2026-11-13T13:18:46Z | changed | running status: Kiro is executing or scheduling nodes → — | [1] 2026-11-13T03:46:58Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/agents-and-automation/workflow-run-statuses/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/agents-and-automation/workflow-run-statuses POST: https://latestn.com/dispute/tool/kiro/agents-and-automation/workflow-run-statuses with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/agents-and-automation/workflow-run-statuses?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What do the different run statuses mean in Kiro workflows? Revision 3, last verified 2026-11-20T13:34:32Z. https://latestn.com/tool/kiro/agents-and-automation/workflow-run-statuses (accessed 2026-11-21T10:06:15Z). @misc{LatestN_tool_kiro_agents_and_automation_workflow_run_statuses_r3, title = {What do the different run statuses mean in Kiro workflows?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/agents-and-automation/workflow-run-statuses}}, note = {Revision 3; digest sha256:48d59558692c7270; last verified 2026-11-20T13:34:32Z; accessed 2026-11-21T10:06:15Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/agents-and-automation/workflow-run-statuses