Answer: The limitations include that turns have no key, sub-agents start a new conversation, requests without kiro.root_conversation_id can't be linked to their parent, kiro.tool_calls and kiro.tool.call count different things, and credits are reported for each request rather than each tool call. Status: Confirmed Entry: tool/kiro/admin-and-enterprise/real-time-events-limitations Revision: 1 Digest: sha256:a6b901433ec324b2 (changes whenever the content changes) Timeline: Created: 2026-11-17T13:49:40Z Last changed: 2026-11-17T13:49:40Z Last verified: 2026-11-20T13:27:19Z Next check: 2026-11-21T13:27:19Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Turns limitation | Turns have no key. | [1] | 2026-11-20 Sub-agent limitation | Sub-agents start a new conversation. | [1] | 2026-11-20 Unlinkable requests | Requests without kiro.root_conversation_id , such as requests from Kiro CLI on the V2 agent engine, can't be linked to their parent. | [1] | 2026-11-20 Tool call counting limitation | kiro.tool_calls and kiro.tool.call count different things. | [1] | 2026-11-20 Credits limitation | Credits are reported for each request, not for each tool call. | [1] | 2026-11-20 Page updated | November 16, 2026 | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Understanding events - Monitor per-user activity - Monitor and track - Enterprise - Docs - Kiro". https://kiro.dev/docs/enterprise/monitor-and-track/user-activity/understanding-events/ Role: primary. Accessed: 2026-11-20T13:27:19Z Quote: "Turns have no key." (Supports: Turns limitation) Quote: "Sub-agents start a new conversation." (Supports: Sub-agent limitation) Quote: "Requests without kiro.root_conversation_id , such as requests from Kiro CLI on the V2 agent engine, can't be linked to their parent." (Supports: Unlinkable requests) Quote: "kiro.tool_calls and kiro.tool.call count different things." (Supports: Tool call counting limitation) Quote: "Credits are reported for each request, not for each tool call." (Supports: Credits limitation) Quote: "Page updated: November 16, 2026" (Supports: Page updated) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: d67ffef4bda5a2838b09ecc0ffdf65b5321f9703de014e52142bc1c8ab329f0d (captured 2026-11-20T13:27:16Z) 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:27:19Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:27:19Z Last attempt: 2026-11-20T13:27:19Z Notes and limitations: Extracted automatically from a single official source (section "Limitations"). Related: https://latestn.com/tool/kiro/admin-and-enterprise/registry-server-overrides How do I override a registry MCP server configuration in Kiro? https://latestn.com/tool/kiro/admin-and-enterprise/remove-models-from-allow-list How do I remove models from the allow list in Kiro? https://latestn.com/tool/kiro/admin-and-enterprise/review-additional-credit-purchases How do I review additional credit purchases in Kiro? https://latestn.com/tool/kiro/admin-and-enterprise/prepare-s3-bucket-for-csv-reports How do I prepare an Amazon S3 bucket for Kiro CSV reports? https://latestn.com/tool/kiro/admin-and-enterprise/prepare-s3-bucket-for-reports What S3 bucket permissions and setup does Kiro require before exporting CSV reports? https://latestn.com/tool/kiro/admin-and-enterprise/prompt-logging-prerequisites What are the prerequisites for enabling prompt logging in Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T13:49:40Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/admin-and-enterprise/real-time-events-limitations/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/admin-and-enterprise/real-time-events-limitations POST: https://latestn.com/dispute/tool/kiro/admin-and-enterprise/real-time-events-limitations with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/admin-and-enterprise/real-time-events-limitations?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the limitations of Kiro real-time user activity events? Revision 1, last verified 2026-11-20T13:27:19Z. https://latestn.com/tool/kiro/admin-and-enterprise/real-time-events-limitations (accessed 2026-11-21T10:08:16Z). @misc{LatestN_tool_kiro_admin_and_enterprise_real_time_events_limitations_r1, title = {What are the limitations of Kiro real-time user activity events?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/admin-and-enterprise/real-time-events-limitations}}, note = {Revision 1; digest sha256:a6b901433ec324b2; last verified 2026-11-20T13:27:19Z; accessed 2026-11-21T10:08:16Z} } 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/admin-and-enterprise/real-time-events-limitations