HTTP request failed
Service
cupixworks-any-voxel-agent
Occurrences
53
Status
Reported
Confidence
85%
Actionability
44%
Cluster ID
bffd5e6c-fb6d-471b-b177-aa8d8621f6e7
First Seen
2026-06-25 08:59 UTC
Last Seen
2026-08-04 19:57 UTC
Actions
HTTP request failed
What Happened#
2026-06-25 17:59 KST cupixworks-any-voxel-agent(ap-southeast-2)가 pointcloud 230896에 대해 PUT /api/v1/pointclouds/230896 호출로 voxel_state 전이를 시도하다 Rails API로부터 HTTP 400 (STAT40000 — State not changed)을 받아 HttpError: HTTP request failed를 throw했다. 같은 pointcloud 가 약 6시간 전(11:57 KST)에 이미 정상 처리된 흔적이 있어, SQS 재배달된 동일 메시지를 다시 처리하다 발생한 멱등성 (idempotency) 결함으로 보인다. 발생 횟수는 1건, 단일 tenant(cupix / team naylorlove)에 국한된다.
Quick Facts#
| Field | Value |
|---|---|
| exception.class | HttpError |
| exception.message | HTTP request failed |
| top_frame | node_modules/@tesla/typescript-node-sdk/.../pointcloudApi.js:3362 |
| upstream_response | 400 Cupix::Errors::InvalidState (STAT40000, "State not changed") |
| api_endpoint | PUT http://api-tesla.cupix.internal/api/v1/pointclouds/230896 |
| runtime | Node.js (filebeat 7.17.15) |
| env | production / ap-southeast-2 |
| tenant | cupix / team naylorlove |
Affected Teams#
| Team / Domain | Error Count | Impact |
|---|---|---|
naylorlove (tenant cupix) |
1 | pointcloud 230896 voxel 처리가 한 차례 실패로 처리되어 voxel_state가 error로 떨어졌을 가능성. 사용자 가시적 데이터 손실은 없음 — 직전 실행이 완료 상태였다면 결과물은 유지됨. |
Timeline#
- 2026-06-25 11:57 KST —
BaseService::runByMessage | id: 230896— 첫 SQS 메시지로 pointcloud 230896 처리 시작.RealityCaptureManager::loadEntityParameters까지 정상 진입 (entity parameters length: 4). 이때updateVoxelState(Aggregating)이 먼저 실행되었음. - 2026-06-25 17:59:00 KST —
BaseService::runByMessage | id: 230896(session3ed3dd6...) — 동일 pointcloud에 대한 두 번째 처리 시작. - 2026-06-25 17:59:00 KST —
PUT /api/v1/pointclouds/230896요청, Rails API가400 STAT40000 "State not changed"응답.HttpError: HTTP request failedthrow. - 2026-06-25 17:59:01 KST —
BaseService::cleanUpAnythingRelatedModel | path: undefined(catch path 진입 후 cleanup), 이어서AwsQueueManager::deleteMessage로 메시지 정상 삭제.
Scoring#
Confidence 85% · Actionability 44%
Confidence#
| Dimension | Score | Detail |
|---|---|---|
| Evidence completeness | 5/5 | 21 code refs, 6 log queries |
| Code path explicitness | 3/3 | 21 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 | 5/5 | trivial |
| Affected files | 1/5 | 18 file(s) |
| Single repo | 1/3 | 7 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 |