ES /docs

failed to get captured area - error: Timed out reading data from server

Service
cupixworks-worker
Occurrences
10
Status
Reported
Confidence
85%
Actionability
52%
Cluster ID
d38c4204-8606-41ab-97b2-150fc3dcf1eb
First Seen
2026-08-06 08:32 UTC
Last Seen
2026-08-06 08:47 UTC
Datadog↗ Slack↗
Actions

failed to get captured area - error: Timed out reading data from server

What Happened#

2026-08-06, production cupixworks-worker(tesla Sidekiq)의 background footprint 계산 경로에서 voxel-service captured_area 호출이 30초 read timeout으로 실패했다. tesla가 Cupix::HttpClient의 DEFAULT_READ_TIMEOUT = 30초 안에 voxel-service Lambda(동기 Athena 쿼리)의 응답을 받지 못해 RestClient::Exceptions::ReadTimeout("Timed out reading data from server")이 발생했고, Cupix::VoxelService.captured_area!의 rescue가 이를 SYS20000으로 재-raise했다. 이 timeout은 Cupix::HttpClient의 재시도 조건(RETRIABLE_STATUS_CODES = [429, 502, 503, 504])에 해당하지 않아 재시도되지 않는다. footprint 계산은 background 작업이며 모든 계층에서 rescue되어 사용자 영향은 없다 → noise (downstream Athena 지연으로 인한 transient/deterministic timeout).

Quick Facts#

Field Value
exception.class Cupix::Errors::System (SYS20000), 원인 RestClient::Exceptions::ReadTimeout
exception.message failed to get captured area - error: Timed out reading data from server
top_frame app/services/cupix/voxel_service.rb:98 (captured_area! rescue)
runtime Ruby / Sidekiq (queue :fresh), tesla
env production, regions us-west-2 / ap-southeast-2

Affected Teams#

Team / Domain Error Count Impact
cupix (internal) 94 (now-14d, class:Facility timeout 로그) background footprint 계산 실패. captured_size/FootprintHistory 갱신 지연. 사용자 요청 실패 아님

Timeline#

  1. 2026-08-06 17:32 KST — 클러스터 first_seen. burst 시작 (production cupixworks-worker).
  2. 2026-08-06 17:47 KST — 클러스터 last_seen. ~15분 창에 10건 수집.
  3. 참고: Facility ID 13은 now-14d 전 기간에 걸쳐 4시간 주기(cron)로 동일 timeout 반복 (84건).

Scoring#

Confidence 85% · Actionability 52%

Confidence#

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