ES /docs

TransferManager::failTask | path: /tmp/workspace/rabren.739490_result/rabren.739490_1463351_ref_plan

Service
cupixworks-capture-3dreconstruction-instance
Occurrences
1
Status
Abandoned
Confidence
85%
Actionability
36%
Cluster ID
c981afb3-fdee-465b-98f6-5cb42e8cd722
First Seen
2026-07-22 01:47 UTC
Last Seen
2026-07-22 01:47 UTC
Actions
현재 상태 abandoned 에서는 실행할 액션이 없습니다.

TransferManager::failTask | path: /tmp/workspace/rabren.739490_result/rabren.739490_1463351_ref_plan

What Happened#

3d-reconstruction agent가 rabren.739490 capture의 ref_planes.json pointcloud resource 를 업로드하기 위해 POST /api/v1/pointclouds/1233204/resources 를 호출했다. 최초 호출은 client-side 에서 ECONNABORTED 로 abort 되었지만 tesla 서버는 이미 plane kind resource 를 생성한 상태였다. 1초 뒤 재시도가 같은 요청을 반복했고, tesla 가 HTTP 400 Duplicate kind: plane 을 반환했으며 TransferManager 는 400 은 retryable 이 아니므로 count: 1/5 에서 failTask 를 호출하고 task 를 실패 처리했다.

Quick Facts#

Field Value
exception.class HttpError
exception.message HTTP request failed (server body: Duplicate kind: plane, code ARG10001)
top_frame node_modules/@tesla/typescript-node-sdk/api/pointcloudApi.js:1040:40
runtime node (agent bundle /tmp/agent/dist)
deploy @tesla/typescript-node-sdk@1.13.3-SNAPSHOT.202605301249_1e9855b03300e7077469e8a23e5d7e36
env production, us-west-2

Affected Teams#

Team / Domain Error Count Impact
rabren (team.id 1242) 1 Capture 739490 의 3d reconstruction 결과 upload 실패 — pointcloud 1233204 의 ref_planes resource 가 client 관점에서 실패 상태로 종료

Timeline#

  1. 2026-07-22 10:47:30 KST — 최초 createResource(POST /pointclouds/1233204/resources, kind=plane) 호출이 ECONNABORTED 로 실패. TransferManager::retryTask 가 1000ms 뒤 재시도 예약 (count: 1/5, code: ECONNABORTED).
  2. 2026-07-22 10:47:31 KST — Retry 로 renew()init() 재실행. Server(tesla) 가 HTTP 400 Duplicate kind: plane (ARG10001) 반환. HttpError: HTTP request failed 로 raise (log id AwAAAZ-HgbFCuHYqjg...).
  3. 2026-07-22 10:47:31 KSTTransferManager::failTask 발화 (count: 1/5, code: undefined, message: HTTP request failed), 이어 BaseTaskContainer::checkTaskFail | Total: 1, Done: 0, Failed: 1.

Scoring#

Confidence 85% · Actionability 36%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 20 code refs, 4 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 22 file(s)
Single repo 1/3 2 service(s)
Immediate actions 0/3 absent
Testability 2/3 test mentioned
External dependency 1/3 external deps found
Data migration 3/3 no migration