This query has been addressed by my colleague Mick in a parallel support ticket you've submitted on the same subject.
For the benefits of other forum members here, below is the response:
For the benefits of other forum members here, below is the response:
We'll be releasing a new version soon (today or tomorrow) that removes that limit. However, please note that there is a known issue with the Google Drive REST API in that uploads that take over an hour will always fail. This is documented in the help file:
"For some cloud services, e.g. Google Drive and Box but not Amazon S3 or Azure, if it takes a long time to upload a file then it may fail because the security token has expired. When SyncBackPro connects to a cloud service it is given a security token that is passed back to the cloud service with every call made. The security tokens are only valid for 60 minutes (usually, although this is service specific) but they can be refreshed and are refreshed automatically by SyncBackPro. However, if it takes longer to upload a file than the security token is valid for then there the upload will always fail as the security token will have expired by the time the upload has completed, and the cloud service will only check the security token once the upload has complete. This is a limitation of those cloud services that use expiring security tokens."
