Free cookie consent management tool by TermsFeed Considerations for Archiving Processes [Process Modeling]
Considerations for Archiving Processes

After a process is completed or canceled, it can be archived. Once a process is archived, the data it contains is no longer available for reporting.

Users with appropriate access would still be able to view the history of an archived process in the Process Activity tab under the Monitor view for auditing purposes. This feature is currently enabled by default for all new Appian Cloud sites starting on Appian 21.1 or later versions and will be enabled on existing Appian Cloud sites via a phased approach.

The default archive interval is seven days after process completion. A process model's archival setting can be set on the Data Management tab in the Process Modeler.


Most completed processes are not needed for system-wide reporting and therefore serve no essential purpose once they've finished processing. Archiving or deleting processes is a good way to clear out unneeded processes and minimize the size of the Appian databases.

Auto-archiving is a default option for processes with data and metadata that need not be retained after completion. Archiving merely provides an option for subsequent unarchiving if legal/regulatory requirements mandate recovery of process information. This setting (7 days) can be changed by the system administrator. Any interval set on the Data Management tab also overrides the default setting for a single Process Model.

Auto-deletion should only be selected for processes that never require the viewing of data or metadata after completion. No trace of deleted processes remain in Appian, once deleted. This option provides maximum space savings in Appian databases (KDBs) and on disk.

If you need to keep a permanent record of process data after completion, process data can be mapped to a separate reporting process or exported to an RDBMS. Process archives contain a great deal of information regarding execution history that becomes unnecessary overhead when performing business-activity reporting.

Archives can be used to provide an audit trail of process execution, but this feature must be implemented with careful consideration of your storage requirements. In general, you should not keep all of your archive files. Doing so can be costly in disk-space usage.

See Managing Process Archives for more information on how to run the archiveprocess script, unarchive processes, and configure other archive settings.


Setting an archive or deletion interval on a subprocess is the same as for any other process. There are additional issues to consider, however.

  • When setting an archive or deletion interval for completed subprocesses, take care not to remove data needed by a parent process before that process completes or before all reporting requirements are met.
  • You might need to redesign the subprocess so that all data is passed back to the parent process, if you need to archive or delete the subprocess on a different schedule than the parent-process.

Policy considerations

Archiving a process frees system memory, but impacts your reports. The data in an archived processes is no longer available for reporting purposes.

If you keep archives of each process, have your system administrator schedule the cleanup script to remove archive files after they are no longer needed.

Historical data

If you have key performance indicators that must be reported on historically, consider creating a separate process for storing this information.


Whenever a process is archived or deleted, the event will be recorded in the removed_processes log.

Open in Github Built: Thu, Jun 13, 2024 (05:02:13 PM)

Considerations for Archiving Processes