ES /docs

[SalesforceWebToCaseWorker] fail to send web to case. reason: 'RestClient error' case_type: 'floorpl

Service
cupixworks-worker
Occurrences
3
Status
Reported
Confidence
80%
Actionability
60%
Cluster ID
8e0baf0f-f2e4-4239-ac82-79b6d3025d6a
First Seen
2026-06-10 00:49 UTC
Last Seen
2026-07-23 06:31 UTC
Datadog↗ Slack↗
Actions

[SalesforceWebToCaseWorker] fail to send web to case. reason: 'RestClient error' case_type: 'floorpl

What Happened#

2026-06-10 09:49:52 KST, cupixworks-worker (Sidekiq) 의 SalesforceWebToCaseWorker 가 Salesforce Web-to-Case endpoint(https://webto.salesforce.com/servlet/servlet.WebToCase) 로 floorplan_update_case POST 요청을 보내던 중 읽기 타임아웃(60초 초과) 으로 실패했다. RestClient 의 read timeout (Net::ReadTimeout) 이 발생하여 RestClient::Exceptions::ReadTimeout 으로 wrapping 되었고, 14일 retention 기간 내 단 1건만 발생한 transient 이벤트로 확인됐다.

Quick Facts#

Field Value
exception.class RestClient::Exceptions::ReadTimeout (wraps Net::ReadTimeout)
exception.message Timed out reading data from server
top_frame app/workers/salesforce_web_to_case_worker.rb:8 (Cupix::HttpClient.post)
downstream https://webto.salesforce.com/servlet/servlet.WebToCase
env production, us-west-2
tenant cupix

Affected Teams#

Team / Domain Error Count Impact
Salesforce integration / Floorplan 1 floorplan_update_case 1건이 Salesforce Case 로 전송되지 않음 (Floorplan model_id 87830). 단, 같은 model_id 87830 에 대해 9초 전 (09:48:44 KST) 동일한 case 전송이 성공한 기록이 있어 사용자/영업 임팩트는 거의 없음 (중복 trigger 로 보이는 두 번째 시도가 실패)

Timeline#

  1. 2026-06-10 09:48:42 KST — SalesforceWebToCaseWorker JID 08c52f7a5647c4d75aa28568 시작 (Floorplan model_id 87830)
  2. 2026-06-10 09:48:44 KST — 위 JID 성공 (send web to case successful, 0.561 sec)
  3. 2026-06-10 09:48:52 KST — SalesforceWebToCaseWorker JID be687e8f81590d6ad02c9709 다시 시작 (동일 Floorplan model_id 87830, 중복 trigger 추정)
  4. 2026-06-10 09:49:52 KST — RestClient read timeout (60.279 sec 후) → 에러 로그 기록 후 worker 정상 종료
  5. 2026-06-10 09:49:52 KST — error-sweeper 가 cluster 생성 (occurrence_count: 1)

Scoring#

Confidence 80% · Actionability 60%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 6 code refs, 6 log queries
Code path explicitness 3/3 6 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 5/5 trivial
Affected files 1/5 16 file(s)
Single repo 1/3 4 service(s)
Immediate actions 0/3 absent
Testability 2/3 test mentioned
External dependency 3/3 no external deps
Data migration 3/3 no migration