ES /docs

[Cupix::Cron::Integration] failed to renew integration: BIM360 Authentication failed:

Service
cupixworks-migration-worker
Occurrences
169
Status
Reported
Confidence
80%
Actionability
32%
Cluster ID
da8a0448-ae4a-4fda-9e5f-54cb0a6e7730
First Seen
2026-07-13 04:07 UTC
Last Seen
2026-07-21 04:07 UTC
Actions

[Cupix::Cron::Integration] failed to renew integration: BIM360 Authentication failed:

What Happened#

BIM360 OAuth 토큰 갱신 cron (Cupix::Cron::Integration.renew_before_expiration) 이 2026-07-13 13:07 KST 실행 도중 특정 BIM360 integration 레코드의 refresh_token 을 Autodesk Forge 로 재발급 요청하다 HTTP 400 Bad Request 응답을 받고 실패했다. 실패한 integration 은 failed 상태로 전이되며 사용자가 재인증하기 전까지 BIM360 연동이 중단된다. 동일 cron 실행 안에서 다수의 다른 BIM360 integration 은 정상 갱신되었으므로 서비스 전반 장애가 아닌 개별 tenant 의 refresh_token 무효화 이슈다.

Quick Facts#

Field Value
exception.class Cupix::Errors::Parameter (code ARG10000)
exception.message BIM360 Authentication failed: (Autodesk developerMessage 필드 비어 있음)
top_frame app/operations/bim360_operation.rb:66-69
runtime Rails on cupixworks-migration-worker (Elastic Beanstalk, service_role: migrationworker)
deploy production-us-west-2-20260713T0407Z0-4f01ffc0-cupixworks
env production, region us-west-2

Affected Teams#

Team / Domain Error Count Impact
BIM360 integration (Autodesk Forge OAuth) 1건 (본 cluster) / 최근 24h 동일 pattern 다수 (integrations 2332, 1160, 1163, 1428, 1234, 1405, 1473, 1482, 1472, 1470 등 10건+) 해당 tenant 의 BIM360 파일/모델 sync 중단, integration statefailed, 사용자 재인증 필요

Timeline#

  1. 2026-07-13 13:07:19 KST — Cron Cupix::Cron::Integration.renew_before_expiration 실행 (매 4시간 :07 스케줄)
  2. 2026-07-13 13:07:19 KSTIntegrationRepository#refresh_tokenBim360Operation.refresh_token 호출, Autodesk Forge 가 HTTP 400 Bad Request 응답
  3. 2026-07-13 13:07:19 KSTRestClient::Exception rescue 진입, BIM360 refresh_token failed: - error: 400 Bad Request 로그 기록 후 Cupix::Errors::Parameter 재발생
  4. 2026-07-13 13:07:19 KSTintegration_repository.rb:135-138 에서 refresh_token_failed_at 갱신 및 failed_state! 로 상태 전이
  5. 2026-07-13 13:07:19 KST — Cron rescue 블록 (integration.rb:10-11) 에서 로그 기록 후 next 로 다음 candidate 계속

Scoring#

Confidence 80% · Actionability 32%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 26 code refs, 5 log queries
Code path explicitness 3/3 26 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 15 file(s)
Single repo 1/3 3 service(s)
Immediate actions 0/3 absent
Testability 0/3 no test info
External dependency 1/3 external deps found
Data migration 0/3 migration needed