ES /docs

ChildProcessManager logs all stderr as errors — AWS SDK v2 warnings

Service
cupixworks-any-bimrevision-agent
Occurrences
648
Status
Dismissed
Confidence
85%
Actionability
16%
Cluster ID
058cbc7f-c18d-4a19-b3f5-809233851bcf
First Seen
2026-06-24 04:44 UTC
Last Seen
2026-08-04 22:13 UTC
Datadog↗ Slack↗
Actions
현재 상태 dismissed 에서는 실행할 액션이 없습니다.

ChildProcessManager logs all stderr as errors — AWS SDK v2 warnings

What Happened#

2026-06-24 13:44 KST에 cupixworks-any-bimrevision-agent 가 BIM revision 비교 작업(bim_id=18044, src_revision_id=24593)을 처리하는 동안 child process(BimCompareProcess) 의 stderr 로 Autodesk Forge AECModelData.json 404 응답 스택트레이스가 그대로 출력되었다. parent 의 ChildProcessManager.setupEventHandlers 는 stderr 전체를 logger.error(...) 로 라인 단위로 받아쓰기 때문에 한 번의 Forge API 404가 수십 줄의 error 레벨 로그로 분해되어 노이즈로 잡혔다. BIM revision 잡 자체는 BimRevisionService::REVISE-END 에서 "status":"success" 로 종료되었다 — 사용자 영향 없음.

Quick Facts#

Field Value
exception.class ForgeUtilsError
exception.message Resource not found: file/urn%3Aadsk.fluent%3Afs.file%3Aautodesk-360-translation-storage-prod%2Fw3cEko2vSNuSmggy9xLMHQ%2F21%2Foutput%2F0%2FAECModelData.json
errorCode API_NOT_FOUND
top_frame @cupixapps/forge-utils/server-utils/forge-client.js:90:31 (ForgeClient.handleApiError)
runtime Node.js child process (forked from BimCompareManager)
package @cupixapps/forge-utils@10.98.0, @cupixapps/forge-agents@10.98.0
env production, us-west-2

Affected Teams#

Team / Domain Error Count Impact
gad (BIM revision agent) 3 (이 cluster) 사용자 영향 없음 — 잡은 정상 종료 (status:success). 로그 노이즈만 발생

Timeline#

  1. 2026-06-24 13:44:07 KST — BimRevisionService::REVISE-BEGIN | bim_id=18044, src_revision_id=24593 (V24), prev_revision_id=24273 (V23) — Forge URN urn:adsk.wipprod:fs.file:vf.w3cEko2vSNuSmggy9xLMHQ (version 20 ↔ 21) 비교 시작
  2. 2026-06-24 13:44:08 KST — child process stderr 에 ForgeUtilsError: Resource not found ... /21/output/0/AECModelData.json 첫 발생 (first_seen)
  3. 2026-06-24 13:44:10 KST — version 20 / version 21 양쪽에 대해 동일한 404 한 번 더 발생 (last_seen, 총 3건)
  4. 2026-06-24 13:46:57 KST — 별개의 bim_id=20016 revision 비교 시작 (관련 없는 후속 잡)
  5. 2026-06-24 13:48:18 KST — BimRevisionService::REVISE-END | bim_id=18044 ... "status":"success", "elapsed_ms":253285 — 404 발생에도 잡은 success 종료

Scoring#

Confidence 85% · Actionability 16%

Confidence#

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