Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resuming synchronize transfer always prompts for action #8601

cyberduck opened this issue Feb 22, 2015 · 1 comment

Resuming synchronize transfer always prompts for action #8601

cyberduck opened this issue Feb 22, 2015 · 1 comment


Copy link

@cyberduck cyberduck commented Feb 22, 2015

172dd00 created the issue

I am attempting to synchronize a local directory with my S3 bucket using the "Upload Only" option. I have enabled automatic retries in Cyberduck preferences under "Connection".

However when the connection fails and attempts to reconnect I am always required to select the transfer type again "Upload Only" before the transfer will continue. It would be very nice if this was remembered since otherwise the intention of the retry option is not as useful.

To reproduce this follow the steps below.

  1. Configure Cyberduck to enable network retries under Preferences -> Connection. Make sure "Repeat failed networking tasks" is selected and number of retries is greater than 0.
  2. Connect to a S3 storage and select the "synchronize" action.
  3. Select a directory to synchronize. Make sure it has enough data to allow for time to fail.
  4. Select "Upload only"
  5. Cause a network failure between the S3 storage and your machine to allow for retry.
  6. Notice that the synchronize will not automatically continue without manual intervention.
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 23, 2015

@dkocher commented

In c02ef77.


@cyberduck cyberduck closed this Feb 23, 2015
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants