Issue: Sometimes, while the application is processing, it takes a while to obtain the result and continue.


Symptoms: 

When performing any function within the system requiring data be obtained from BIM 360, there can be an unusually long wait. For example, in the Members tab pressing on a project to display project members usually takes a second or two or three to get the results. However, it can occasionally take two or three times that amount of time or longer—maybe as long as 30 seconds or more.


Cause:

This appears to involve the ability of the Autodesk Forge APIs to return a result. Since this occurs randomly at different times, it may have to do with system load or availability.


Resolution:

None at this time, other than to wait for the process to continue.


Issue: When uploading files, the BIM 360® Updated By field is not assigned. 


Symptoms: 

When viewing an uploaded document on BIM 360® or from BIMrx® Cloud Manager Browse, the Updated By username field is blank. Also, when using BIMrx® Cloud Manager to export to MS Excel the Uploaded By field displays ‘**None**’. 


Cause:

This appears to be an issue with the Forge API.


Resolution:

None at this time, other than recognizing a blank value indicates an automated upload.


Issue: Sometimes a file won't upload if the folder containing it is being accessed by the windows file explorer. 


Symptoms: 

Sometimes a file won’t upload when it is added by BIMrx® Cloud Manager. 


Cause:

It appears to be caused by the file explorer accessing the file location in the local folder structure. However, this behavior is not entirely consistent and will often work normally despite this situation.


Resolution:

Fix is to just try again, after either closing the file explorer or navigating to a difference folder outside of the current hierarchy.