DRAFT KB-[SP-4610] Process variables unexpectedly set to null after asynchronous subprocess runs

Symptoms

Process variables unexpectedly appear null after an asynchronous sub-process node completes, even though non-null output is expected:

Cause

The asynchronous sub-process was once synchronous and had an output variable that was not deleted. The output variable was not removed when the process became asynchronous. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-96059.

Workaround

1. Convert the subprocess to synchronous.
2. Remove the output variable.
3. Convert back to asynchronous.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2020