Deposit remote save
Overview
After a file is uploaded, the box records it on the backend before anchoring. A failed record can be retried without sending the file again.
How it works
Each upload target fills task.remoteFile. A SaveRemoteFile stage then calls POST /files/save. BCYIP storage only needs { fileId } and does not POST a second time. A response without id fails the task, so anchoring does not start. If task.fileId is still missing at anchor time, the pipe rejects with a clear message. Backend 400 responses about fileId or Bcyip-Agent map to the same guidance.
Key files
src/services/fileProtect/saveRemoteFile.pipe.ts— save stagesrc/services/fileProtect/remoteFile.ts— payload built from the upload targetsrc/services/fileProtect/anchor.pipe.ts— missing file id guard
Technical decisions
Local copy goes through mapFromPromise. successFromPromise marked the task successful before remoteFile was stored, so the next stage never ran.