Skip to main content
maggie.deppewalker
Employee
October 14, 2026

KB-2412 Health Check Fails With "Unable to Generate the Data Collection Zip File (APNX-1-4520-203)" Due to Malformed CSV Records in removed_processes_db*.csv

Symptoms

  1. Health Check execution fails during the data collection phase with error: "Unable to generate the data collection zip file (APNX-1-4520-203)"
  2. The following errors appear in health-check.log: 
    Skipping record in <APPIAN_HOME>/logs/audit/removed_processes_db_PX###_YYYY-MM-DD_HHMM.csv: Text 'Timestamp' could not be parsed at index 0
    java.io.UncheckedIOException: IOException reading next record: java.io.IOException: (line X) invalid char between encapsulated token and delimiter
  3. Log stack traces point to RemovedProcessesAggregatedDataProcessor.getInputStream() and org.apache.commons.csv.Lexer.parseEncapsulatedToken()
  4. Issue began occurring starting in Appian version 26.7 or later

Cause

The RemovedProcessesAggregatedDataProcessor, introduced in Appian 26.7, fails to handle certain exceptions when processing removed_processes_db_*.csv audit files.

The processor only catches exceptions during record processing logic, but does not catch specific exceptions thrown when it encounters structurally malformed CSV records.

When malformed records exist (such as unescaped quotes in Process Display Name expressions logged to the CSV) specific exceptions are thrown that cause the entire Health Check to fail.

Action

Apply the latest hotfix to your Appian installation. The fix is available in Appian 26.8.135.0 and later.

Workaround

Self-Managed

  1. Until the hotfix is applied, you can work around this issue by correcting any invalid Process Display Name configurations in your process models that contain unescaped quotes or other characters that produce malformed CSV entries.
  2. After correcting the process model configurations, manually edit or remove the problematic removed_processes_db_*.csv files from the <APPIAN_HOME>/logs/audit/ directory.

Note: deleting audit data may need specific server permissions.

Preventative Actions

After applying the fix, review all Process Display Name configurations across your process models to ensure they use valid expressions that do not contain unescaped special characters. Reference the Process Display Name documentation for proper configuration guidelines.

Affected Versions

This article applies to Appian 26.7, 26.8, and 26.9.

Last Reviewed: October 2026

 

    Terms & ConditionsAccessibility statement