Skip to main content
Version: 4.37.2

Retry remote file save without re-uploading

Version: 4.37.2 Date: 2026-10-21

Goal: Do not anchor a document without a fileId when saving the remote record fails, and allow that save to be retried without uploading the file again.

Solution: New SaveRemoteFile stage after Upload. Each target fills task.remoteFile (BCYIP with { fileId } only). The stage fails if remoteFile is missing; the backend validates the rest on POST /files/save. BCYIP passes through the stage without a second POST. A response without id fails and does not anchor. The local copy uses mapFromPromise: successFromPromise marked the task successful before remoteFile was stored, so the next stage never started.

Files Modified:

  • src/services/fileProtect/fileProtect.types.ts
  • src/services/fileProtect/remoteFile.ts
  • src/services/fileProtect/saveRemoteFile.pipe.ts
  • src/services/fileProtect/index.ts
  • src/services/fileProtect/uploadHandlers/sharepoint.pipe.ts
  • src/services/fileProtect/uploadHandlers/gcpStorage.pipe.ts
  • src/services/fileProtect/uploadHandlers/azureBlob.pipe.ts
  • src/services/fileProtect/uploadHandlers/local.pipe.ts
  • src/services/fileProtect/uploadHandlers/bcyip.pipe.ts

Release fragment: fix-retry-remote-save