ES /docs

RestClient::BadGateway: 502 Bad Gateway

Service
cupixworks-rest_client
Occurrences
15
Status
Reported
Confidence
85%
Actionability
36%
Cluster ID
71191f8b-a22e-4f2d-be76-56462159a21d
First Seen
2024-08-22 09:25 UTC
Last Seen
2026-08-05 04:05 UTC
Actions

RestClient::BadGateway: 502 Bad Gateway

What Happened#

2026-07-22 ~ 2026-07-27 사이 cupixworks-api(tesla) 에서 PixgenieInferenceOperation#record_results_from_bulk_result 가 pix genie backoffice API 로 결과를 기록하려다 반복 실패했다. backoffice 는 payload 의 seg_id 를 정수로 요구하지만 tesla 는 "seg-0001" 같은 문자열을 보냈고, review_key/level_id/record_id 등 필수 필드가 nil 이었다. backoffice 는 422 검증 오류를 반환했고, tesla 는 이를 Cupix::Errors::BadGateway → HTTP 502 로 변환했다.

Quick Facts#

Field Value
exception.class Cupix::Errors::BadGateway (Error Tracking 상 RestClient::BadGateway 로 표기, stale)
exception.message Failed to record pix genie results to backoffice: Cupix::Errors::BadGateway: [{"type"=>"int_parsing", "loc"=>["body","annotations",0,"seg_id"], "msg"=>"Input should be a valid integer, unable to parse string as an integer", "input"=>"seg-0001"}, ...]
top_frame app/operations/pixgenie_base_operation.rb:136 (handle_error else branch)
runtime Ruby on Rails (tesla)
env production

Affected Teams#

Team / Domain Error Count Impact
pix genie (console inference/review) 15 (Datadog 로그, now-14d) / 14 (Error Tracking) pix genie 추론 결과가 backoffice 에 기록되지 않음

Timeline#

  1. 2024-08-22 18:25 KST — Error Tracking 이슈 first_seen (Representative Error 502 Bad Gateway, stale)
  2. 2026-07-22 ~ 2026-07-27record_results_from_bulk_result 에서 422 검증 오류가 502 로 반복 집계
  3. 2026-07-24 16:28 KST — 이슈 last_seen (Cupix::Errors::BadGateway seg_id 파싱 오류)
  4. 2026-08-04 — RCA 수행. Representative Error 와 실제 최근 메시지 불일치 확인

Scoring#

Confidence 85% · Actionability 36%

Confidence#

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