Trimble Connect User Forum

• For some reason sync tool doesn't recognize that some files have been updated on local or cloud. This just means that sync completes without any errors but some files don't get synchronized. This is of course really bad and means that we need to spend more time for checking than manually adding files.
• Some files have conflicts every single time we try to upload/download them. This typically happens with big (>50mb) IFC files. Other file types seem to work much better. This is also very annoying from management point of view because it means that someone needs to always confirm steps solving conflict. It also happens so that if we solve conflict and resync after that conflict is bag so we totally lose functionality that files are only uploaded/downloaded when they have been updated.

• Delete local chases
  • This doesn't make any difference
• Set up sync on different computer
  • This doesn't make any difference. And probably suggest that something strange is happening on the cloud.
• Set up only upload or download sync schedules instead of bi-directional.
  • This doesn't make any difference
• Checked that the files are not open anywhere
  • This has been the case that the files are not open

• For some reason sync tool doesn't recognize that some files have been updated on local or cloud. This just means that sync completes without any errors but some files don't get synchronized. This is of course really bad and means that we need to spend more time for checking than manually adding files.
• Some files have conflicts every single time we try to upload/download them. This typically happens with big (>50mb) IFC files. Other file types seem to work much better. This is also very annoying from management point of view because it means that someone needs to always confirm steps solving conflict. It also happens so that if we solve conflict and resync after that conflict is bag so we totally lose functionality that files are only uploaded/downloaded when they have been updated.

• Delete local chases
  • This doesn't make any difference
• Set up sync on different computer
  • This doesn't make any difference. And probably suggest that something strange is happening on the cloud.
• Set up only upload or download sync schedules instead of bi-directional.
  • This doesn't make any difference
• Checked that the files are not open anywhere
  • This has been the case that the files are not open

• For some reason sync tool doesn't recognize that some files have been updated on local or cloud. This just means that sync completes without any errors but some files don't get synchronized. This is of course really bad and means that we need to spend more time for checking than manually adding files.
• Some files have conflicts every single time we try to upload/download them. This typically happens with big (>50mb) IFC files. Other file types seem to work much better. This is also very annoying from management point of view because it means that someone needs to always confirm steps solving conflict. It also happens so that if we solve conflict and resync after that conflict is bag so we totally lose functionality that files are only uploaded/downloaded when they have been updated.

• Delete local chases
  • This doesn't make any difference
• Set up sync on different computer
  • This doesn't make any difference. And probably suggest that something strange is happening on the cloud.
• Set up only upload or download sync schedules instead of bi-directional.
  • This doesn't make any difference
• Checked that the files are not open anywhere
  • This has been the case that the files are not open

Hi Tom.

Unless there are new problems we have addressed current issues and fixes are (hopefully) soon available. 

If others have similar problems, please report those to your local service team. This way we get more evidence. Regards, Kai 

• For some reason sync tool doesn't recognize that some files have been updated on local or cloud. This just means that sync completes without any errors but some files don't get synchronized. This is of course really bad and means that we need to spend more time for checking than manually adding files.
• Some files have conflicts every single time we try to upload/download them. This typically happens with big (>50mb) IFC files. Other file types seem to work much better. This is also very annoying from management point of view because it means that someone needs to always confirm steps solving conflict. It also happens so that if we solve conflict and resync after that conflict is bag so we totally lose functionality that files are only uploaded/downloaded when they have been updated.

• Delete local chases
  • This doesn't make any difference
• Set up sync on different computer
  • This doesn't make any difference. And probably suggest that something strange is happening on the cloud.
• Set up only upload or download sync schedules instead of bi-directional.
  • This doesn't make any difference
• Checked that the files are not open anywhere
  • This has been the case that the files are not open

Hi Tom.

Unless there are new problems we have addressed current issues and fixes are (hopefully) soon available. 

If others have similar problems, please report those to your local service team. This way we get more evidence. Regards, Kai 

• For some reason sync tool doesn't recognize that some files have been updated on local or cloud. This just means that sync completes without any errors but some files don't get synchronized. This is of course really bad and means that we need to spend more time for checking than manually adding files.
• Some files have conflicts every single time we try to upload/download them. This typically happens with big (>50mb) IFC files. Other file types seem to work much better. This is also very annoying from management point of view because it means that someone needs to always confirm steps solving conflict. It also happens so that if we solve conflict and resync after that conflict is bag so we totally lose functionality that files are only uploaded/downloaded when they have been updated.

• Delete local chases
  • This doesn't make any difference
• Set up sync on different computer
  • This doesn't make any difference. And probably suggest that something strange is happening on the cloud.
• Set up only upload or download sync schedules instead of bi-directional.
  • This doesn't make any difference
• Checked that the files are not open anywhere
  • This has been the case that the files are not open

• Allow the upload of the new file in local that has same name as deleted file in server.
• Prevent messages in case of file attributes updates - which don't have any impact on Sync process. 

Hi Tom.

Unless there are new problems we have addressed current issues and fixes are (hopefully) soon available. 

If others have similar problems, please report those to your local service team. This way we get more evidence. Regards, Kai 

• For some reason sync tool doesn't recognize that some files have been updated on local or cloud. This just means that sync completes without any errors but some files don't get synchronized. This is of course really bad and means that we need to spend more time for checking than manually adding files.
• Some files have conflicts every single time we try to upload/download them. This typically happens with big (>50mb) IFC files. Other file types seem to work much better. This is also very annoying from management point of view because it means that someone needs to always confirm steps solving conflict. It also happens so that if we solve conflict and resync after that conflict is bag so we totally lose functionality that files are only uploaded/downloaded when they have been updated.

• Delete local chases
  • This doesn't make any difference
• Set up sync on different computer
  • This doesn't make any difference. And probably suggest that something strange is happening on the cloud.
• Set up only upload or download sync schedules instead of bi-directional.
  • This doesn't make any difference
• Checked that the files are not open anywhere
  • This has been the case that the files are not open