The size of a knowledge center as seen on the front end (/design) does not match the size of the same knowledge center on the back end (disk).
For example, when an Appian Cloud site has high disk usage, Appian Support may provide the breakdown of folder sizes on disk:
Top 10 largest KC folders and IDsDisk Space | Knowledge Center
When searching by folder ID in /design, these numbers do not match.
The mismatch in Knowledge Center size on the front and back end does not have negative functional impact, and is expected and intended product behavior to preserve disk I/O performance.
Appian does not move files from their original location on the filesystem. Instead, Appian stores information about each file in a metadata pointer in the Content Engine (CO). The data stored in the Content Engine is what is displayed in /design. When files are moved on the front end, the file metadata pointer is updated in the Content Engine, but not on the filesystem, thus causing the size displayed on the front and back end to differ.
There is no action or workaround as this is intentional product behavior.
If document cleanup is required for high disk usage, Appian Support can provide a mapping of files in the largest back end Knowledge Center. To request a mapping of individual files in the largest back end Knowledge Center, please create a Support Case.
Appian Cloud customers can request an enhancement to the disk breakdown report provided by Appian Support to reduce confusion. If you would like to be added to this enhancement, please create a Support Case referencing AN-249476.
This article applies to all versions of Appian.
Last Reviewed: January 2024