In this mode, the transfer service enumerates items and streams per-file SAS URLs to the client,
which then transfers each file using the Transfer Engine (Azure.Storage.Blobs).
When cancelled, triggers a graceful server-side cancellation of the transfer job.
The SDK calls the cancel endpoint once and keeps draining the command stream until the server
confirms the job is cancelled. This is distinct from the method-level cancellation token which
immediately stops SDK-side processing. Defaults to
None (no cancellation).
If a file transfer does not complete within this duration, it is reported as failed. What happens
next differs per direction: on upload the timeout is terminal — the file is not attempted again,
so this really is the whole budget for one file; on download it is retried in place under
TransferRetryPolicyDefinition, the behavior download has always had. The proper
retry policy unifying the two will be implemented in REL-1302802.
The value is absolute and does not scale with file size, which means a large file over a slow link
can be unable to finish within it however healthy the transfer is. At 100 Mbit/s a 50 GB file needs
roughly 67 minutes, so the 15-minute default fails it on every run. Raise this when the corpus
holds files whose size divided by the expected throughput exceeds the timeout.
TODO: this shape is an open design question, deliberately left as is for now. An absolute per-file
budget fits no corpus of mixed sizes — it is wildly generous for a 1 KB file and unreachable for a
large one, and the danger is that the failure is silent in review and deterministic in production:
every run fails the same big files, and the one knob an operator would reach for has to be guessed
from the corpus and the link. The candidate replacement is a deadline derived from the item's size,
roughly clamp(floor, base + size / assumed-throughput, ceiling), leaving this property as an
explicit override. Settle it BEFORE this type becomes public — changing what the value means
afterwards is a breaking change for anyone who has tuned it.
Gets or sets the retry policy applied per file on the V2 path.
Defaults to
ExponentialPolicy with a 2 second base
delay and 3 retries. A retry only happens for errors classified as retryable: a locked file on
either direction, and additionally a per-file timeout on download only — see
PerFileTimeout.