CaptureIntelligenceProcessManager timeout과 SQS visibility timeout 동기화 오류

I'll run the RCA skill on this cluster.

I'll analyze the cluster and produce an RCA report.

This is a routine SQS error log file (not malware) — it's a cluster artifact from the error-sweeper

Let me check the status board first, then look up the searching-datadog-logs skill and repo-mapping.

This is part of an active service incident. There are 3 clusters arriving simultaneously at 05:03:32

Not malware — error cluster artifact. Continuing.

Not malware. The 505db6d9 cluster has the same SQS receipt handle in the message — same root cause a

Not malware. This is a previously-completed RCA report for a sibling cluster sharing the same root c

Let me verify the repo for `cupixworks-capture-intelligence-agent` and check the key code paths cite

Good — repo is `cupixworks/applications/agents`. Let me verify the key files cited.

Code matches what the sibling RCA cited. Now I have all evidence I need. Note: this cluster's repres

RCA written to `/home/ec2-user/error-sweeper/content/docs/incidents/607be229-428b-4596-9cb0-9a672cc5

I'll run the RCA skill on this cluster.

I'll read the cluster file and start the RCA investigation.

This file is a cluster error report (RCA input data), not malware. I'll proceed with the RCA investi

Recent (resolved) service-degradation incident with 2 sibling clusters. I'll proceed with normal RCA

The service is in cupixworks monorepo. Let me find the agent code.

This is benign infrastructure code (AWS SQS queue manager). Continuing analysis.

Code is benign service infrastructure. Let me check the constants for QueueVisibilityTimeout.

Constants file is benign. Let me search Datadog for related logs.

Found the error at 14:03:32 KST (= 05:03:32 UTC). The error is unique and isolated — only 1 occurren

Let me get just the timeframe immediately around 14:03:32 with status filter:

I now have a clear picture. The timeline:

Code is benign business logic for spawning Python child processes. Now I have enough evidence:

Good — sibling RCAs already point to the timeout chain. Now I have all the data. Let me write the re

KST conversion: 2026-06-19T05:03:32.903Z = 2026-06-19 14:03:32 KST.

A previous RCA already exists. I'll overwrite with the new analysis.

RCA report written to `content/docs/incidents/607be229-428b-4596-9cb0-9a672cc5ac1e/rca.mdx`.

I'll search for the StructuredOutput tool definition.

RCA 완료. 보고서는 `content/docs/incidents/607be229-428b-4596-9cb0-9a672cc5ac1e/rca.mdx`에 작성되었고, structure