ES /docs

CaptureIntelligenceProcessManager timeout과 SQS visibility timeout 동기화 오류

Service
cupixworks-capture-intelligence-agent
Occurrences
3
Status
Dismissed
Confidence
80%
Actionability
44%
Cluster ID
607be229-428b-4596-9cb0-9a672cc5ac1e
First Seen
2026-06-19 05:03 UTC
Last Seen
2026-08-01 01:45 UTC
Actions
현재 상태 dismissed 에서는 실행할 액션이 없습니다.

CaptureIntelligenceProcessManager timeout과 SQS visibility timeout 동기화 오류

What Happened#

2026-06-19 14:03:32 KST, cupixworks-capture-intelligence-agent (us-west-2 production)에서 SQS 메시지 4f9fc010-9b09-43cf-b0e0-bb2588254514를 처리하던 중 Python 자식 프로세스가 1시간 timeout에 도달하여 abort되었다. 에러 처리 경로에서 AwsQueueManager::deleteMessage가 호출되었으나, 메시지의 SQS visibility timeout(600초)이 이미 만료되어 ReceiptHandle is invalid. Reason: The receipt handle has expired. 에러가 발생했다. 동일 메시지는 이후 14:07:10 KST에 재전달되어 정상 처리되었다.

Quick Facts#

Field Value
exception.class AWS.SQS InvalidParameterValue (ReceiptHandle expired)
exception.message The receipt handle has expired.
top_frame packages/base/src/manager/aws-queue.manager.ts:99
runtime Node.js (aws-sdk v2 SQS)
env production / us-west-2

Affected Teams#

Team / Domain Error Count Impact
clark-vdc / capture-intelligence-agent 1 단건 처리 1회 실패 후 SQS 자동 재전달로 정상 복구 (capture summary 생성 약 4분 지연)

Timeline#

  1. 2026-06-19 13:0x KST 부근 — Python summary 분석 프로세스 spawn (capture summary 작업)
  2. 2026-06-19 14:03:32 KSTCaptureIntelligenceProcessManager | process timeout, aborting... (TIMEOUT_MS = 1시간 도달)
  3. 2026-06-19 14:03:32 KSTCaptureIntelligenceProcess | process error: The operation was aborted
  4. 2026-06-19 14:03:32 KSTCupixAuth::handleError | Undefined response: AbortError ... Process timeout
  5. 2026-06-19 14:03:32 KSTBaseService::handlingMessageErrorsdeleteByMessage 호출 (ApproximateReceiveCount=1)
  6. 2026-06-19 14:03:32 KSTAwsQueueManager::deleteMessage | end - ... receipt handle has expired (본 cluster의 root error log)
  7. 2026-06-19 14:07:10 KST — 동일 MessageId 4f9fc010-... SQS 재전달 후 정상 처리 완료 (deleteMessage | end - message id: 4f9fc010-9b09-43cf-b0e0-bb2588254514)

Scoring#

Confidence 80% · Actionability 44%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 15 code refs, 6 log queries
Code path explicitness 3/3 15 file:line refs
Log evidence 2/3 section, query
RCA structure 3/3 3/3 sections
Revision history 0/3 0 revision(s)
Agent execution 3/3 success

Actionability#

Dimension Score Detail
Fix complexity 5/5 trivial
Affected files 1/5 11 file(s)
Single repo 1/3 11 service(s)
Immediate actions 0/3 absent
Testability 0/3 no test info
External dependency 1/3 external deps found
Data migration 3/3 no migration