Answer: On the Schedule page, open a job and switch to its Logs tab to inspect a failed run; expand the run to read its trace, and for a run marked Error or Timeout you can use Ask the agent to open a new chat with a report already in the composer. Status: Confirmed Entry: tool/kiro/troubleshooting/inspect-failed-cron-run Revision: 3 Digest: sha256:d0ca21925bf4ac5f (changes whenever the content changes) Timeline: Created: 2026-11-13T03:38:43Z Last changed: 2026-11-20T13:23:21Z (Ask the agent availability: Error or Timeout → A run marked Error or Timeout also offers Ask the agent .) Last verified: 2026-11-20T13:23:21Z Next check: 2026-11-21T13:23:21Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of Where to inspect | On the Schedule page, open a job and switch to its Logs tab. | | [1] | 2026-11-20 Run badges | OK , Error , Timeout , or Cancelled | | [1] | 2026-11-20 Trace | Expand a run to read its trace. | | [1] | 2026-11-20 Ask the agent availability | A run marked Error or Timeout also offers Ask the agent . | | [1] | 2026-11-20 Output tail length | 4,000 characters | characters | [1] | 2026-11-20 Rerun command | kirocrew cron trigger | | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Scheduling - Features - Crew - Docs - Kiro". https://kiro.dev/docs/crew/features/cron/ Role: primary. Accessed: 2026-11-20T13:23:21Z Quote: "On the Schedule page, open a job and switch to its Logs tab." (Supports: Where to inspect) Quote: "Each run is listed with an OK , Error , Timeout , or Cancelled badge, its start time, duration, trigger, and summary." (Supports: Run badges) Quote: "Expand a run to read its trace." (Supports: Trace) Quote: "A run marked Error or Timeout also offers Ask the agent ." (Supports: Ask the agent availability) Quote: "the tail of the run output (the last 4,000 characters)" (Supports: Output tail length) Quote: "use Run Now or kirocrew cron trigger for that." (Supports: Rerun command) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 433a1b3c17509664abc5b29235c3e6386c6f7fa53e243be7e010c2e28e10bd00 (captured 2026-11-20T13:23:20Z) 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:23:21Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:23:21Z Last attempt: 2026-11-20T13:23:21Z Notes and limitations: Extracted automatically from a single official source (section "Inspect a failed run"). Related: https://latestn.com/tool/kiro/troubleshooting/kgl-common-errors What are common KGL errors in Kiro and how do I fix them? https://latestn.com/tool/kiro/troubleshooting/kirocrew-command-not-found How do I fix the kirocrew: command not found error after installing Kiro Crew? https://latestn.com/tool/kiro/troubleshooting/manifest-validation-rules What validation rules apply to a Kiro Crew app manifest? https://latestn.com/tool/kiro/troubleshooting/hook-performance-issues How do I resolve performance issues caused by Kiro hooks? https://latestn.com/tool/kiro/troubleshooting/hook-shell-command-errors How do I fix shell command errors in Kiro hooks? https://latestn.com/tool/kiro/troubleshooting/important-migration-changes What important changes should I know about when upgrading from Q CLI to Kiro CLI? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:23:21Z | changed | Ask the agent availability: Error or Timeout → A run marked Error or Timeout also offers Ask the agent . | [1] 2026-11-20T13:23:21Z | changed | Trace: Expand a run to read its trace → Expand a run to read its trace. | [1] 2026-11-20T13:23:21Z | changed | Where to inspect: On the Schedule page, open a job and switch to its Logs tab → On the Schedule page, open a job and switch to its Logs tab. | [1] 2026-11-17T13:44:43Z | changed | Rerun command: — → kirocrew cron trigger | [1] 2026-11-17T13:44:43Z | changed | Output tail length: — → 4,000 characters | [1] 2026-11-17T13:44:43Z | changed | Ask the agent availability: — → Error or Timeout | [1] 2026-11-17T13:44:43Z | changed | Trace: — → Expand a run to read its trace | [1] 2026-11-17T13:44:43Z | changed | Run badges: — → OK , Error , Timeout , or Cancelled | [1] 2026-11-17T13:44:43Z | changed | Where to inspect: — → On the Schedule page, open a job and switch to its Logs tab | [1] 2026-11-17T13:44:43Z | changed | rerun command: kirocrew cron trigger → — | [1] 2026-11-17T13:44:43Z | changed | output tail length: 4,000 characters → — | [1] 2026-11-17T13:44:43Z | changed | failed run option: Ask the agent → — | [1] 2026-11-17T13:44:43Z | changed | how to read trace: Expand a run to read its trace → — | [1] 2026-11-17T13:44:43Z | changed | run badges: OK , Error , Timeout , or Cancelled → — | [1] 2026-11-17T13:44:43Z | changed | where to inspect: On the Schedule page, open a job and switch to its Logs tab → — | [1] 2026-11-13T03:38:43Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/troubleshooting/inspect-failed-cron-run/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/troubleshooting/inspect-failed-cron-run POST: https://latestn.com/dispute/tool/kiro/troubleshooting/inspect-failed-cron-run with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/troubleshooting/inspect-failed-cron-run?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I inspect a failed cron run in Kiro Crew? Revision 3, last verified 2026-11-20T13:23:21Z. https://latestn.com/tool/kiro/troubleshooting/inspect-failed-cron-run (accessed 2026-11-21T10:02:50Z). @misc{LatestN_tool_kiro_troubleshooting_inspect_failed_cron_run_r3, title = {How do I inspect a failed cron run in Kiro Crew?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/troubleshooting/inspect-failed-cron-run}}, note = {Revision 3; digest sha256:d0ca21925bf4ac5f; last verified 2026-11-20T13:23:21Z; accessed 2026-11-21T10:02:50Z} } 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/troubleshooting/inspect-failed-cron-run