ES /docs

ChildProcessManager::setupEventHandlers | Child process stderr: at BIMSVF2Manifest.init (/tmp/ag

Service
cupixworks-any-bimrevision-agent
Occurrences
13
Status
Dismissed
Confidence
85%
Actionability
60%
Cluster ID
268a4eb1-affd-4f12-8c42-62c6b339eafa
First Seen
2026-07-06 18:51 UTC
Last Seen
2026-08-04 22:13 UTC
Actions
현재 상태 dismissed 에서는 실행할 액션이 없습니다.

ChildProcessManager::setupEventHandlers | Child process stderr: at BIMSVF2Manifest.init (/tmp/ag

What Happened#

2026-07-07 03:51 ~ 03:58 KST 사이에 cupixworks-any-bimrevision-agent (tenant cupix, team gilbaneco, us-west-2) 에서 BIM revision 비교 작업 2건이 ForgeUtilsError: Invalid OTG manifest 로 실패했다. Autodesk Forge/APS 가 반환한 SVF2 OTG manifest 파일이 검증에 실패했기 때문이며, 두 실패 모두 동일한 BIM (bim_id: 20418) 의 서로 다른 revision (25054, 25056) 에서 발생했다. 사용자 관점에서는 두 revision 이 bim_comparison_state=error 로 상태 코드 REV1 (UNKNOWN) 을 받았다.

Quick Facts#

Field Value
exception.class ForgeUtilsError
exception.message Invalid OTG manifest
exception.errorCode INVALID_OTG_MANIFEST
top_frame @cupixapps/forge-utils/convert-utils/svf2/svf2-manifest.js:77:30 (BIMSVF2Manifest.init)
runtime Node.js child process (fork), forge-utils@10.98.0, forge-agents@10.98.0
env production, region us-west-2, tenant cupix, team gilbaneco

Affected Teams#

Team / Domain Error Count Impact
gilbaneco (bim_id 20418) 2 BIM revision 비교 2건 실패 (revision 25054, 25056), bim_comparison_state=error (REV1)

Timeline#

  1. 2026-07-07 03:51:08 KST — Revision 25054 (bim_id 20418) 처리 시작, AwsS3Manager 구성
  2. 2026-07-07 03:51:11 KSTREVISE-BEGIN 로그 기록, runBimCompare 호출 (formatType: svf2, previousFormatType: svf)
  3. 2026-07-07 03:51:13 KST — Child process 에서 ForgeUtilsError: Invalid OTG manifest 발생, INVALID_OTG_MANIFEST 로 종료. REV1 로 매핑되어 REVISE-END status=error (elapsed_ms=3204)
  4. 2026-07-07 03:58:14 KST — Revision 25056 (bim_id 20418) child process fork
  5. 2026-07-07 03:58:17 KST — 동일한 ForgeUtilsError: Invalid OTG manifest 재현, REVISE-END status=error (elapsed_ms=2985)
  6. 2026-07-07 03:58:18 ~ 03:58:23 KST — 별개 BIM (bim_id: 20420, revision 25055) 은 정상 처리 후 REVISE-END status=success

Scoring#

Confidence 85% · Actionability 60%

Confidence#

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