Should not --max-duration stop new transfers when reached?

What is the problem you are having with rclone?

I've run a copy command with a --max-duration of 12h.
When it reached 12h, rclone output that reached the deadline but continued transferring and starting new transfers. As of now, it has completed 16h and still starting and finishing new transfers

According to changelog "Add --max-duration flag to control the maximum duration of a transfer session (boosh)" the transfer session should be stopped
Also, the flags document as "Maximum duration rclone will transfer data for."

But the main docs says "Rclone will stop scheduling new transfers when it has run for the duration specified." Pointing that the limit is for schedule and not for transfer and since all files where scheduled at start it will finish them all even if this means starting new transfers after the deadline.

Is the observed behavior the expected? My expectation was that after the deadline, no new transfers would be started regardless when it was scheduled.

What is your rclone version (output from rclone version)

rclone v1.52.2

  • os/arch: windows/amd64
  • go version: go1.14.4

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Windows 10 64bit

Which cloud storage system are you using? (eg Google Drive)


The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone copy -v --max-duration 12h H:\isos\x OneDrive-luizamericop:emuisos/x

The rclone config contents with secrets removed.

type = onedrive
token = {"access_token":"xxx"}
drive_id = yyyy
drive_type = personal

A log from the command with the -vv flag

Paste  log here

Any transfer in progress would finish if it started before the duration.

Any new transfer would not happen if the duration is exceeded.

If you have an issue with a new transfer starting after the deadline, please share a debug log.

Done at

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.