failed to get captured area - error: 500 Internal Server Error
Service
cupixvista-api-migration-worker
Occurrences
230
Status
Reported
Confidence
80%
Actionability
16%
Cluster ID
a558bd06-2374-433b-968a-5e17dfd21a2f
First Seen
2026-07-15 12:36 UTC
Last Seen
2026-07-30 08:41 UTC
Actions
failed to get captured area - error: 500 Internal Server Error
What Happened#
2026-07-15 21:36 KST 부터 21:42 KST 사이에 cupixvista-api-migration-worker (tesla 리포지토리, CUPIXVISTA launch mode, migrationworker role) 에서 Cupix::Cron::Facility.flush_stale_captured_size 크론이 실행되면서 downstream voxel-service Lambda 로의 PUT /captured_area 호출이 5회 연속 500 Internal Server Error 를 반환했다. Lambda 응답 본문을 확인한 결과, 원인은 Athena GetQueryExecution API 에서 발생한 ThrottlingException: Rate exceeded 였다. 영향을 받은 facility 는 최소 5건(ID 604, 607, 609, 610, 612)이며, captured_size 갱신이 실패해 stale 상태로 남았다.
Quick Facts#
| Field | Value |
|---|---|
| exception.class | Cupix::Errors::System (code SYS20000) |
| exception.message | failed to get captured area - error: 500 Internal Server Error |
| top_frame | app/services/cupix/voxel_service.rb:99 |
| downstream | voxel-service Lambda → Athena GetQueryExecution ThrottlingException |
| runtime | Ruby 3.3.7 (rest-client/2.1.0) |
| env | production, us-west-2, tenant=cupix, launch_mode=CUPIXVISTA |
Affected Teams#
| Team / Domain | Error Count | Impact |
|---|---|---|
| cupixvista-api-migration-worker | 5 | 5개 facility 의 captured_size 갱신 실패 (state=stale 유지) |
동일 svc:cupixvista-api-migration-worker::unknown scope 아래 진행 중인 status board 인시던트 에는 관련 클러스터 3개(a558bd06..., fe12d217..., 3a8d30cc...)가 묶여 있다.
Timeline#
- 2026-07-15 21:31 KST — 매 4시간 :31분에 실행되는
flush_stale_captured_size크론이 기동 (스케줄:31 */4 * * *). - 2026-07-15 21:36 KST — Facility 604 부터
Flushing stale captured size로그 시작, 첫 실패 발생. - 2026-07-15 21:38 ~ 21:42 KST — Facility 604, 607, 609, 610 순차 실패 (
500 Internal Server Error). - 2026-07-15 21:42:20 ~ 21:42:28 KST — voxel-service Lambda 가 초당 여러 건의
Athena ThrottlingException: Rate exceeded (max retries: 3)응답 반환. - 2026-07-15 21:44:41 KST — Facility 612 는 downstream 이 이번엔
503 Service Unavailable반환 (동일 fingerprint 의 sister clusterfe12d217...로 분류).
Scoring#
Confidence 80% · Actionability 16%
Confidence#
| Dimension | Score | Detail |
|---|---|---|
| Evidence completeness | 5/5 | 14 code refs, 3 log queries |
| Code path explicitness | 3/3 | 14 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 | 1/5 | critical |
| Affected files | 1/5 | 15 file(s) |
| Single repo | 1/3 | 2 service(s) |
| Immediate actions | 0/3 | absent |
| Testability | 0/3 | no test info |
| External dependency | 1/3 | external deps found |
| Data migration | 0/3 | migration needed |