Status, progress and resuming
Read the state of a transfer and continue the same job instead of starting a new one.
You need
The pipeit CLI (Linux, macOS, Windows), signed in, and the rights each command needs.
pipeit status
pipeit monitor --direction out
pipeit transfer status TRANSFER-ID --json
pipeit transfer resume TRANSFER-ID --timeout 20m --jsonmonitor keeps running unless you set a timeout. For scripts, pipeit monitor --json --interval 1s --timeout 5m fits; every line is a complete JSON object.
transfer status, wait and resume work with jobs known on this machine. They are not a global search for other people’s IDs. For files, resume uses the kept cipher cache; for directory streams the original sources must stay unchanged.
Related guides
- Command line and servers
Send several files as one transfer
Use a group transfer when you want one acceptance for many files, and resume it with the same ID.
Solve transfer problems
Check the specific problem instead of starting over: a quick decision list and the common symptoms with their next step.
Resuming: acknowledgement, checkpoint and receipt are different
Five signals that sound alike and mean different things, and what resuming actually keeps.
Still stuck?
Check the troubleshooting guide first. If that does not help, tell us what happened.