KB-2287 The folder size varies between the back end and front end

pauline.delacruz — Wed, 24 Jan 2024 14:44:55 GMT

Current Revision posted to Appian Knowledge Base by pauline.delacruz on 1/24/2024 2:44:55 PM

Symptoms

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 IDs

Disk Space | Knowledge Center

When searching by folder ID in /design, these numbers do not match.

Cause

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.

Action

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.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2024

Tags: integration, knowledge centers

KB-2287 Folder size is different on the back end and the front end

pauline.delacruz — Wed, 24 Jan 2024 14:43:12 GMT

Revision 7 posted to Appian Knowledge Base by pauline.delacruz on 1/24/2024 2:43:12 PM

Symptoms

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 IDs

Disk Space | Knowledge Center

When searching by folder ID in /design, these numbers do not match.

Cause

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.

Action

There is no action or workaround as this is intentional product behavior.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2024

Tags: integration, knowledge centers

[DRAFT SP-9091] KB-XXXX Folder size is different on back end and front end

pauline.delacruz — Wed, 03 Jan 2024 22:12:55 GMT

Revision 6 posted to Appian Knowledge Base by pauline.delacruz on 1/3/2024 10:12:55 PM

Symptoms

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 IDs

Disk Space | Knowledge Center

When searching by folder ID in /design, these numbers do not match.

Cause

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.

Action

There is no action or workaround as this is intentional product behavior.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2024

Tags: integration, knowledge centers

[DRAFT SP-9091] KB-XXXX Folder size is different on back end and front end

pauline.delacruz — Wed, 03 Jan 2024 22:12:46 GMT

Revision 5 posted to Appian Knowledge Base by pauline.delacruz on 1/3/2024 10:12:46 PM

Symptoms

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 IDs

Disk Space | Knowledge Center

When searching by folder ID in /design, these numbers do not match.

Cause

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.

Action

There is no action or workaround as this is intentional product behavior.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2023

Tags: integration, knowledge centers

[DRAFT SP-9091] KB-XXXX Folder size is different on back end and front end

pauline.delacruz — Wed, 03 Jan 2024 22:10:04 GMT

Revision 4 posted to Appian Knowledge Base by pauline.delacruz on 1/3/2024 10:10:04 PM

Symptoms

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 IDs

Disk Space | Knowledge Center

When searching by folder ID in /design, these numbers do not match.

Cause

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.

Action

There is no action or workaround as this is intentional product behavior.

Appian Cloud customers can request an enhancement to the disk breakdown report provided by Solution Engineering to reduce confusion. If you would like to be added to this enhancement, please create a Support Case referencing AN-249476.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2023

Tags: integration, knowledge centers

[DRAFT SP-9091] KB-XXXX Folder size is different on back end and front end

Maggie Deppe-Walker — Tue, 19 Dec 2023 21:45:09 GMT

Revision 3 posted to Appian Knowledge Base by Maggie Deppe-Walker on 12/19/2023 9:45:09 PM

Symptoms

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 IDs

Disk Space | Knowledge Center

When searching by folder ID in /design, these numbers do not match.

Cause

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.

Action

There is no action or workaround as this is intentional product behavior.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2023

KB-XXXX Folder size is different on back end and front end

Maggie Deppe-Walker — Tue, 19 Dec 2023 21:42:17 GMT

Revision 2 posted to Appian Knowledge Base by Maggie Deppe-Walker on 12/19/2023 9:42:17 PM

Symptoms

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 IDs

Disk Space | Knowledge Center

When searching by folder ID in /design, these numbers do not match.

Cause

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.

Action

There is no action or workaround as this is intentional product behavior.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2023

KB-XXXX Folder size is different on back end and front end

Maggie Deppe-Walker — Tue, 19 Dec 2023 21:38:06 GMT

Revision 1 posted to Appian Knowledge Base by Maggie Deppe-Walker on 12/19/2023 9:38:06 PM

Symptoms

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 IDs

Disk Space | Knowledge Center

When searching by folder ID in /design, these numbers do not match.

Cause

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 file information in a metadata pointer in the Content Engine. 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 to differ in display on the front and back end.

Action

There is no action or workaround as this is intentional product behavior.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2023