ES /docs

BaseService::handlingMessageErrors | Error and message object - {"error":{"errno":-110,"code":"ETIME

Service
cupixworks-capture-postprocessor-agent
Occurrences
4
Status
Reported
Confidence
80%
Actionability
52%
Cluster ID
b5e7eb6b-f647-453c-8004-b811af8dad27
First Seen
2026-06-24 14:13 UTC
Last Seen
2026-07-15 09:13 UTC
Datadog↗ Slack↗
Actions

BaseService::handlingMessageErrors | Error and message object - {"error":{"errno":-110,"code":"ETIME

What Happened#

2026-06-24 23:13 KST에 cupixworks-capture-postprocessor-agent가 SQS 메시지(MessageId: c5b275f1-...) 처리 중 Tesla API 호출에서 read ETIMEDOUT (errno -110)을 만나 BaseService::handlingMessageErrors 에러를 기록했다. 16분 뒤 같은 서비스의 다른 워커에서 동일한 errno/code/syscall 형태의 시스템 레벨 네트워크 오류가 한 번 더 발생했고, 두 케이스 모두 메시지가 즉시 삭제되지 않고 SQS 재시도 큐로 돌아갔다.

Quick Facts#

Field Value
exception.class BaseService::handlingMessageErrors
exception.message read ETIMEDOUT (Node.js system error, errno -110, syscall: read)
top_frame packages/base/src/base-service.ts:311
underlying_origin CupixAuth::handleError (packages/api/src/authentication/cupix-auth.ts:54) — TLS read on Tesla API auth call
env production, regions us-west-2, eu-central-1
tenant cupix

Affected Teams#

Team / Domain Error Count Impact
gad / capture-postprocessor pipeline 2 두 개의 SQS 메시지가 즉시 삭제되지 않고 재시도 큐로 환류. MessageId c5b275f1 은 약 45 분 후 ApproximateReceiveCount: 2 로 재처리되었으나 여전히 undefined response 로 실패

Timeline#

  1. 2026-06-24 23:13:04 KST — MessageId c5b275f1-1081-43fa-99a8-51de8c74fe44 처리 중 Tesla API auth 호출에서 read ETIMEDOUT 발생. CupixAuth::handleError | Undefined response warn → BaseService::handlingMessageErrors error (ApproximateReceiveCount=1).
  2. 2026-06-24 23:18:44 KST — 같은 서비스의 다른 메시지(2e2194ec-...)가 Cannot read properties of undefined (reading 'response') 로 실패 (별개 패턴, 같은 인시던트 윈도).
  3. 2026-06-24 23:29:46 KST — 두 번째 시스템 에러: MessageId 7ae02df1-28dd-4c16-9b69-dc7d937dd817, errno -104 ECONNRESET, syscall: read (cluster의 두 번째 occurrence).
  4. 2026-06-24 23:57:51 KST — c5b275f1 메시지가 ApproximateReceiveCount: 2 로 재처리되었고 이번엔 undefined response 로 다시 실패 후 삭제됨.

Scoring#

Confidence 80% · Actionability 52%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 21 code refs, 5 log queries
Code path explicitness 3/3 21 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 10 file(s)
Single repo 1/3 8 service(s)
Immediate actions 0/3 absent
Testability 0/3 no test info
External dependency 3/3 no external deps
Data migration 3/3 no migration