ES /docs

ForgeService::handlingMessageErrors | Errors in error handling - {"response":{"statusCode":403,"body

Service
cupixworks-any-forge-agent
Occurrences
3
Status
Reported
Confidence
85%
Actionability
52%
Cluster ID
d3b016bd-cc1e-4b25-af13-ace2db09d6ab
First Seen
2026-05-12 06:15 UTC
Last Seen
2026-06-24 23:31 UTC
Actions

ForgeService::handlingMessageErrors | Errors in error handling - {"response":{"statusCode":403,"body

What Happened#

2026-05-12 06:15:52–06:15:56 UTC 사이 cupixworks-any-forge-agent(ap-northeast-1)에서 BIM 업로드 SQS 메시지 처리 중 원본 에러가 발생했고, 이어지는 에러 핸들러가 tesla API에 상태 업데이트(PUT /api/v1/bims/{id}, forge_state: Error)를 시도했으나 동일한 403 PERM33000 Cupix::Errors::PermissionDenied ("Updating entity on billing expired team/workspace is not allowed")가 반환되어 핸들러 내부의 중첩 try/catch에서 "Errors in error handling" 로그로 기록되었다. 총 2건 (bim id 219, 220), 동일 테넌트(cupix)에서 발생.

Quick Facts#

Field Value
exception.class HttpError
exception.message Updating entity on billing expired team/workspace is not allowed (PERM33000)
top_frame packages/cupix-tesla-forge-agent/src/forge-service.ts:407
runtime Node.js (cupix-tesla-forge-agent)
env production, ap-northeast-1

Affected Teams#

Team / Domain Error Count Impact
cupixworks-any-forge-agent (BIM forge translation) 2 빌링 만료된 team/workspace의 BIM 업로드 요청이 실패 시 agent가 상태를 Error로 반영하지 못함 — BIM forge_state가 원래 값(예: Processing)에 머물 가능성
tesla (cupixworks-api) 2 PERM33000 반환 (정상 동작, 의도된 검증)

Timeline#

  1. 2026-05-12 06:15:52 UTC — bim id 220, bim_revision 253에 대해 runByMessagesPUT /api/v1/bim_revisions/253 → 403 PERM33000
  2. 2026-05-12 06:15:52 UTChandlingMessageErrorsupdateBimForgeState(220, Error) 시도 → 동일한 403 PERM33000 → "Errors in error handling" 로그
  3. 2026-05-12 06:15:56 UTC — bim id 219, bim_revision 252에 대해 동일 시나리오 재현

Scoring#

Confidence 85% · Actionability 52%

Confidence#

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