ES /docs

failed to get element records - error: Timed out connecting to server

Service
cupixworks-api
Occurrences
1
Status
Reported
Confidence
85%
Actionability
44%
Cluster ID
e72fe8cd-c550-48db-9eb9-3ee27567803c
First Seen
2026-07-08 12:58 UTC
Last Seen
2026-07-08 12:58 UTC
Actions

failed to get element records - error: Timed out connecting to server

What Happened#

2026-07-08 21:58 KST, cupixworks-api production (us-west-2) 에서 GET /api/v1/siteinsights/element_records 요청 하나가 502 로 실패했다. 원인은 하위 Siteinsights microservice (AWS API Gateway) 로의 TCP 연결이 60초 동안 열리지 않아 RestClient::Exceptions::OpenTimeout 이 발생한 것. 14일 retention 안에서 동일 exception 은 총 3건 (2개 엔드포인트) 뿐이라 systemic 이슈가 아니라 transient network/upstream 이벤트로 판단된다.

Quick Facts#

Field Value
exception.class Cupix::Errors::System (원인: RestClient::Exceptions::OpenTimeout)
exception.message failed to get element records - error: Timed out connecting to server
top_frame app/services/cupix/siteinsights_service.rb:118
code SYS20000
deploy production-us-west-2-20260708T0836Z0-5c918141-cupixworks
env production, region us-west-2
duration 60027.9 ms (Net::HTTP default open_timeout = 60s)

Affected Teams#

Team / Domain Error Count Impact
clark-vdc (team_id 87) 1 단일 사용자(sebastian.boyle@clarkconstruction.com)의 facility_key=3fq7tj element_records 페이지네이션 요청 1건이 502 응답. UI 상 재시도 후 정상 응답 가능성이 높다.

Timeline#

  1. 2026-07-08 17:36 KST — 최신 배포(production-us-west-2-20260708T0836Z0-5c918141-cupixworks) 반영.
  2. 2026-07-08 21:58:57 KSTApi::V1::ElementRecordsController#index 가 Siteinsights #{service_url}/element_records 호출을 시작. TCP connect 실패로 60,027.9 ms 후 RestClient::Exceptions::OpenTimeout 발생.
  3. 2026-07-08 21:58:57 KSTCupix::Errors::System (SYS20000) 로 rescue 되어 502 응답. 후속 재시도 로그 없음(즉시 해소된 것으로 보임).

Scoring#

Confidence 85% · Actionability 44%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 11 code refs, 6 log queries
Code path explicitness 3/3 11 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 16 file(s)
Single repo 1/3 5 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