Some non-Discovery project files (such as geometry file formats) split data over multiple files. When synching such local project files to the cloud, only one file is uploaded to the cloud and any additional files associated with the project may not be uploaded. Workaround: There is no workaround. This behavior is a current limitation in the cloud. [981316]

When solving in Explore, fidelity settings may cause the GPU to run out of memory and start using the CPU resulting in slow solve times. Workarounds: Adjust fidelity slider to a lower position. Disabling shared memory may also be a workaround (see https://nvidia.custhelp.com/app/answers/detail/a_id/5490). [984450]

When replacing a file (containing comments) with a new file (without comments) using the same name, the comments from the original file may remain. Workaround: Use a different file name. [1010914]

When working with defined variations and reopening a project that was created in a different language, there may be remnant artifacts that remain in the original language. Workaround: Rename the parameter in the Parameters table. [1030722]

When a fluid-solid heat transfer simulation is solved in Refine with thermal conductance set on the default contact group, subsequent solves will retain the conductance effect after thermal conductance is turned off. Workaround: Create your own contact or contact group rather than relying on the default. OR if the simulation has been solved in Refine with thermal conductance set on the default contact group, create new user-defined contacts or contact groups on those pairs from which you want to remove thermal conductance before solving again. This can be done for all contact pairs. [1031334]