ES /docs

failed to calculate captured size for Facility ID: 594, error: failed to get captured area - error:

Service
cupixvista-api-migration-worker
Occurrences
395
Status
Reported
Confidence
85%
Actionability
32%
Cluster ID
fe12d217-509c-4320-b68e-d1ec5c4460b2
First Seen
2026-07-15 12:33 UTC
Last Seen
2026-07-30 08:46 UTC
Datadog↗ Slack↗
Actions

failed to calculate captured size for Facility ID: 594, error: failed to get captured area - error:

What Happened#

2026-07-15 21:33~21:44 KST 사이 CUPIXVISTA 마이그레이션 워커(cupixvista-api-migration-worker)에서 총 8건의 Facility#calculate_captured_size 호출이 실패했다. 실패한 facility는 594, 597, 599, 604, 607, 609, 610, 612이고, downstream voxel service(captured_area Lambda)의 응답이 500 또는 503으로 반환되어 상위 rescue 블록에서 failed to calculate captured size for Facility ID: N, error: failed to get captured area - error: ... 로그가 기록되었다.

본 cluster는 status-board가 동일 svc-scope incident 2026-07-15-svc-cupixvista-api-migration-worker--unknown-1로 묶은 3개 cluster (a558bd06, 3a8d30cc, fe12d217) 중 상위 wrapper 로그에 해당한다. Downstream 근본 원인은 이미 sibling cluster 3a8d30cc-330a-4d70-8ac8-5ce4883bc982의 RCA에서 확정되었다: voxel Lambda가 Athena GetQueryExecution을 sleep 없이 폴링해 ThrottlingException을 유발한 것.

Quick Facts#

Field Value
exception.class rescue in Facility#calculate_captured_size (하위 예외는 Cupix::Errors::System code SYS20000)
exception.message `failed to calculate captured size for Facility ID: {id}, error: failed to get captured area - error: {503
top_frame app/models/concerns/voxel_module.rb:22
downstream AWS Lambda voxel/captured_area (data-pipeline-functions)
downstream_error ThrottlingException on GetQueryExecution (max retries: 3) — 일부는 API Gateway 503
env production, us-west-2, tenant cupix (CUPIXVISTA)

Affected Teams#

Team / Domain Error Count Impact
cupixvista-api-migration-worker 8 (본 cluster) Facility 594, 597, 599, 604, 607, 609, 610, 612의 captured_size migration 실패

동일 svc-scope incident로 묶인 관련 cluster:

  • a558bd06-2374-433b-968a-5e17dfd21a2f — downstream 500 시나리오 wrapper
  • 3a8d30cc-330a-4d70-8ac8-5ce4883bc982 — downstream 503 시나리오 (하위 Cupix::VoxelService.captured_area! 로그)

Timeline#

  1. 2026-07-15 21:33 KST — Facility 594: 503 (cluster first_seen)
  2. 2026-07-15 21:36 KST — Facility 597: 500
  3. 2026-07-15 21:38 KST — Facility 599: 500
  4. 2026-07-15 21:39 KST — Facility 604: 500
  5. 2026-07-15 21:41 KST — Facility 607: 503
  6. 2026-07-15 21:42 KST — Facility 609, 610: 500 (동시)
  7. 2026-07-15 21:44 KST — Facility 612: 503 (cluster last_seen)
  8. 2026-07-15 21:49 KST — voxel Lambda 정상 응답 회복 (sibling RCA 로그 근거)

Scoring#

Confidence 85% · Actionability 32%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 13 code refs, 3 log queries
Code path explicitness 3/3 13 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 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