Hello,

This issue in most cases it is related to Windows file system limitations during configuration download.

At the Download configuration stage, Clio pulls a large configuration package from the site and unpacks it locally inside the Workspace, creating a deep folder structure under .application\net-core\core-bin\.... If the Workspace is located on a mapped or network drive (like W:\...) or inside a long directory path, the full file paths can quickly exceed the Windows maximum path length limit (around 260 characters).

When this happens, Windows may fail to correctly create files or directories, and instead of a clear “path too long” message, Clio returns generic .NET errors such as “Stream was too long” or “The filename, directory name, or volume label syntax is incorrect”. The strange fragment like Codes": [] is usually not an actual filename, but a side effect of the path-length failure causing the exception message to appear corrupted or incomplete.

The most reliable solution is to move the Workspace to a very short local path, for example C:\ws\sitename, and avoid using mapped/network drives.

In most cases, shortening the Workspace path resolves both errors and allows the configuration download to complete successfully.

Anastasiia Zhmud, Hello

I’d like to add an observation: this issue occurs only with Creatio instances deployed on Linux. For Creatio sites running on Windows, the configuration is downloaded correctly without any issues.

Is there a way to enable more detailed logging in Clio to see where exactly and why the error occurs?

Hello, 

We have checked with RmD team . The plan to create possibility to switch Creatio web-version into dark mode has been already registered. We will add your customer voice to highlight impotency of such functionality to develop it in future Creatio versions. 

Unfortunately we are unable to provide you with ETA for now. 

Thank you for improving Creatio!