BaseService::handlingMessageErrors | Error and message object - {"error":"undefined response","sqsMe
Service
cupixworks-capture-preprocessor-agent
Occurrences
238
Status
Reported
Confidence
85%
Actionability
36%
Cluster ID
87d46153-c3f0-43ad-b7bc-d821fcb18943
First Seen
2026-06-24 20:30 UTC
Last Seen
2026-08-05 00:05 UTC
Datadog
SlackActions
BaseService::handlingMessageErrors | Error and message object - {"error":"undefined response","sqsMe
What Happened#
cupixworks-capture-preprocessor-agent 가 SQS 메시지를 처리하던 중 PreprocessorService.checkSupportedVideo 의 도메인 검증에서 "Lens covered video detected." Error 가 발생했고, BaseService::handlingMessageErrors 가 이 에러의 원인을 식별하지 못해 error: "undefined response" 형태의 에러 로그를 남겼다. 2026-06-25 05:30 KST 와 06:19 KST 두 차례 발생했으며, 클러스터 fingerprint 기준 24시간 내 같은 패턴(빈 error.response)으로만 따지면 3회까지 관측된다.
Quick Facts#
| Field | Value |
|---|---|
| exception.class | Error (plain new Error(reason)) |
| exception.message | Lens covered video detected. |
| top_frame | packages/cupix-capture-preprocessor-agent/src/preprocessor-service.ts:865 |
| logged as | BaseService::handlingMessageErrors | Error and message object - {"error":"undefined response", ...} |
| env | production, us-west-2 |
Affected Teams#
| Team / Domain | Error Count | Impact |
|---|---|---|
| mortenson / capture preprocessing | 2 | "lens covered" 검증에 걸린 capture 의 실패 원인이 로그에서 "undefined response" 로만 보이므로, 운영자가 외부 의존성 문제로 오인할 수 있음. 실제 capture 처리 자체는 정상적으로 실패 처리된다. |
Timeline#
- 2026-06-25 05:30:20 KST —
CupixAuth::handleError | Undefined response: ... "Lens covered video detected." ...warn 로그 (sqsMessageb8c093e5-b871-408a-a749-54cd0612bc47) - 2026-06-25 05:30:21 KST —
BaseService::handlingMessageErrors | Error and message object - {"error":"undefined response", ...}error 로그 (cluster first_seen) - 2026-06-25 06:19:08 KST — 동일 패턴 warn 로그 (sqsMessage
31e700b7-08e1-4533-b7cb-945fd37ae748) - 2026-06-25 06:19:09 KST — 동일 패턴 error 로그 (cluster last_seen)
- 2026-06-25 06:27:17–18 KST — 동일 패턴 한 차례 더 (sqsMessage
fabaeded-ba68-45cc-a2cc-0ccd47a129de); cluster 집계는 2건이지만 패턴은 지속됨
Scoring#
Confidence 85% · Actionability 36%
Confidence#
| Dimension | Score | Detail |
|---|---|---|
| Evidence completeness | 5/5 | 20 code refs, 5 log queries |
| Code path explicitness | 3/3 | 20 file:line refs |
| Log evidence | 3/3 | section, query, pattern |
| 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 | 1/5 | critical |
| Affected files | 1/5 | 11 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 |