If a file transfer is disrupted due to a network failure, limited server capacity, or other problems likely to be temporary, ExpeDat Desktop will pause for about one minute and then try to repeat the pending transaction.
Some problems, such as network connectivity or busy files, may require user action to resolve. Check the message box of the main window for specific errors.
If the network or server is disrupted during an upload, the server will enforce a mandatory 60 second cooling-off period before that upload can be resumed. Clicking "Retry-Now" prior to the end of this period may fail with a message indicating that the file may be in use.
If you believe the problem is likely to resolve itself in time, such as for the server being at capacity, the recommended action is to wait for ExpeDat Desktop to retry automatically. This gives the network and server time to recover from the original error. If you believe you have resolved the problem, select "Retry Now" to repeat the previous transaction immediately.
If the target is a host group, ExpeDat Desktop will search for an available server amongst the group. This may result in some files being delivered to or downloaded from different servers. If the target includes fallback groups, the fallback servers will be used only if all servers in the earlier peer groups are completely unreachable. If servers in a peer group are reachable but at full capacity, ExpeDat Desktop will retry within that group until capacity becomes available.
ExpeDat Desktop will continue to retry until it succeeds, a fatal error occurs, or you skip or abort the remaining files.
To stop the attempt and return ExpeDat Desktop to an idle state, select "Abort All".
Selecting "Skip Current" will abandon the current transaction and move on to the next transaction. This may be useful if you have queued multiple transactions and believe the error affects only the current one.
When transferring files without Object Handlers or Streaming Folders, ExpeDat Desktop will attempt to preserve data already transferred by resuming at the point of disruption. If an upload to an Object Handler is interrupted, the entire object must restarted from the beginning. If a Streaming Folder is interrupted, that entire folder must be restarted from the beginning.
See Resuming for more details.