ES /docs

BIM360 Authentication failed: Connection reset by peer

Service
cupixworks-worker
Occurrences
1
Status
Reported
Confidence
80%
Actionability
36%
Cluster ID
f758639a-c97a-4dc8-af7f-20814a89c51c
First Seen
2026-06-09 00:07 UTC
Last Seen
2026-06-09 00:07 UTC
Datadog↗ Slack↗
Actions

BIM360 Authentication failed: Connection reset by peer

What Happened#

2026-06-09 09:07:21 KST에 cupixworks-worker의 Cupix::Cron::Integration.renew_before_expiration 크론이 BIM360 integration(5324)의 OAuth refresh token을 갱신하던 중 Autodesk Forge OAuth 엔드포인트와의 TCP 연결이 reset되어 Errno::ECONNRESET("Connection reset by peer")이 발생했다. 이 예외는 Cupix::HttpClient.post에서 재시도되지 않고 Bim360Operation.refresh_token의 rescue StandardError 브랜치까지 전파되었으며, IntegrationRepository#refresh_token이 integration 5324를 failed_state로 영속화했다. 1회 발생.

Quick Facts#

Field Value
exception.class Errno::ECONNRESET (RestClient → Cupix::Errors::BadGateway BG10001로 wrap)
exception.message Connection reset by peer
top_frame app/operations/bim360_operation.rb:72 (Bim360Operation.refresh_token)
caller app/repositories/integration_repository.rb:128
schedule config/schedule.rb:94 — every '7 */4 * * *'
env production, us-west-2
affected integration bim360 integration id=5324

Affected Teams#

Team / Domain Error Count Impact
BIM360 integration (cupixworks-worker) 1 Integration #5324 1건이 failed 상태로 전이됨. 해당 tenant의 BIM360 연동 작업이 사용자가 재인증할 때까지 중단됨.

Timeline#

  1. 2026-06-09 09:07:21 KST — Cupix::Cron::Integration.renew_before_expiration 가 만료 예정 integration들을 처리.
  2. 2026-06-09 09:07:21 KST — Bim360Operation.refresh_token 가 Autodesk Forge refresh_url로 POST 호출 중 TCP 연결 reset.
  3. 2026-06-09 09:07:21 KST — Bim360Operation.refresh_token 의 rescue StandardError가 Cupix::Errors::BadGateway 로 raise. IntegrationRepository#refresh_token 이 integration 5324를 failed_state! 로 변경 후 재raise.
  4. 2026-06-09 09:07:21 KST — Cupix::Cron::Integration.renew_before_expiration 의 rescue StandardError 가 [Cupix::Cron::Integration] failed to renew integration: Connection reset by peer 로그 후 다음 candidate로 진행.

Scoring#

Confidence 80% · Actionability 36%

Confidence#

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