KB-2111 "Does not exist: Process" error thrown when accessing a process instance

Elly Meng — Wed, 24 Nov 2021 20:48:09 GMT

Current Revision posted to Appian Knowledge Base by Elly Meng on 11/24/2021 8:48:09 PM

Symptoms

When accessing a process instance via the Monitoring tab, the following error is thrown:

Load Error
Errors
This process diagram could not be opened due to the following errors.
Does not exist: Process

When using the Start Process smart service, such as within a Web API, the following error is returned:

Error when parsing process details or variables

The following error is printed in the application server log in both instances above:

ERROR com.appiancorp.expr.server.reaction.smartservicebridge.SmartServiceBridgeReaction - Exception occurred during activation of ReactionFunction {key='sys.smartService.start-process-2', class='com.appiancorp.expr.server.reaction.smartservicebridge.PluginSmartServiceBridgeReaction'}
...
Caused by: com.appiancorp.suiteapi.process.exceptions.InvalidProcessException: Does not exist: Process

Cause

The process instance has been archived or deleted.

Action

If the process has been archived and its data is needed by the parent process, follow the steps outlined in KB-1186 to unarchive the process instance.
Adjust archival/deletion thresholds in the Data Mangement tab to allow future process instances to be maintained for the desired amount of time after completion.

Note: Increasing the length of time process instances are maintained before archival/deletion can increase system memory and disk resource utilization of the Appian environment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2021

Tags: process models, application design, processes

KB-2111 "Does not exist: Process" error thrown when accessing a process instance

Parmida Borhani — Thu, 30 Apr 2020 03:53:23 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 4/30/2020 3:53:23 AM

Symptoms

When accessing a process instance via the Monitoring tab, the below error is thrown:

Load Error
Errors
This process diagram could not be opened due to the following errors.
Does not exist: Process

A similar error is printed in the application server log:

ERROR com.appiancorp.expr.server.reaction.smartservicebridge.SmartServiceBridgeReaction - Exception occurred during activation of ReactionFunction {key='sys.smartService.start-process-2', class='com.appiancorp.expr.server.reaction.smartservicebridge.PluginSmartServiceBridgeReaction'}
...
Caused by: com.appiancorp.suiteapi.process.exceptions.InvalidProcessException: Does not exist: Process

Cause

The process instance has been archived or deleted.

Action

If the process has been archived, follow the steps outlined in KB-1186 to unarchive the process instance.
Adjust archival/deletion thresholds in the Data Mangement tab to allow future process instances to be maintained for the desired amount of time after completion.

Note: Increasing the length of time process instances are maintained before archival/deletion can increase system memory and disk resource utilization of the Appian environment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2020

Tags: process models, application design, processes

[SP-3981] DRAFT KB-XXXX "Does not exist: Process" error thrown when accessing a process instance

Parmida Borhani — Wed, 29 Apr 2020 04:36:53 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 4/29/2020 4:36:53 AM

Symptoms

When accessing a process instance via the Monitoring tab, the below error is thrown:

Load Error
Errors
This process diagram could not be opened due to the following errors.
Does not exist: Process

A similar error is printed in the application server log:

ERROR com.appiancorp.expr.server.reaction.smartservicebridge.SmartServiceBridgeReaction - Exception occurred during activation of ReactionFunction {key='sys.smartService.start-process-2', class='com.appiancorp.expr.server.reaction.smartservicebridge.PluginSmartServiceBridgeReaction'}
...
Caused by: com.appiancorp.suiteapi.process.exceptions.InvalidProcessException: Does not exist: Process

Cause

The process instance has been archived or deleted.

Action

If the process has been archived, follow the steps outlined in KB-1186 to unarchive the process instance.
Adjust archival/deletion thresholds in the Data Mangement tab to allow future process instances to be maintained for the desired amount of time after completion.

Note: Increasing the length of time process instances are maintained before archival/deletion can increase system memory and disk resource utilization of the Appian environment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2020

Tags: process models, application design, processes

[SP-3981] DRAFT KB-XXXX "Does not exist: Process" Error thrown in application server log, or when accessing a process instance

James Lee — Mon, 27 Apr 2020 21:44:41 GMT

Revision 7 posted to Appian Knowledge Base by James Lee on 4/27/2020 9:44:41 PM

Symptoms

When accessing a process instance via the Process Monitoring tab, the below error is thrown:

Load Error
Errors
This process diagram could not be opened due to the following errors.
Does not exist: Process

A similar error is printed in the application server stdOut log:

ERROR com.appiancorp.expr.server.reaction.smartservicebridge.SmartServiceBridgeReaction - Exception occurred during activation of ReactionFunction {key='sys.smartService.start-process-2', class='com.appiancorp.expr.server.reaction.smartservicebridge.PluginSmartServiceBridgeReaction'}
...
Caused by: com.appiancorp.suiteapi.process.exceptions.InvalidProcessException: Does not exist: Process

Cause

The process instance has been archived or deleted

Action

If the process has been archived, follow steps outlined in KB-1186 to unarchive the process instance.
Adjust archival/deletion thresholds in the Data Mangement tab to allow future process instances to be maintained for the desired amount of time after completion.

Note: increasing the length of time Process Instances are maintained before archival/deletion can increase system memory and disk resource utilization for your Appian environment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2020

Tags: process models, application design, processes

[SP-3981] DRAFT KB-XXXX "Does not exist: Process" Error thrown in application server log, or when accessing a process instance

James Lee — Mon, 27 Apr 2020 21:43:59 GMT

Revision 6 posted to Appian Knowledge Base by James Lee on 4/27/2020 9:43:59 PM

Symptoms

When accessing a process instance via the Process Monitoring tab, the below error is thrown:

Load Error
Errors
This process diagram could not be opened due to the following errors.
Does not exist: Process

A similar error is printed in the application server stdOut log:

ERROR com.appiancorp.expr.server.reaction.smartservicebridge.SmartServiceBridgeReaction - Exception occurred during activation of ReactionFunction {key='sys.smartService.start-process-2', class='com.appiancorp.expr.server.reaction.smartservicebridge.PluginSmartServiceBridgeReaction'}
...
Caused by: com.appiancorp.suiteapi.process.exceptions.InvalidProcessException: Does not exist: Process

Cause

The process instance has been archived or deleted

Action

If the process has been archived, follow steps outlined in KB-1186 to unarchive the process instance.
Adjust archival/deletion thresholds in the Data Mangement tab to allow future process instances to be maintained for the desired amount of time after completion. Note increasing the length of time Process Instances are maintained before archival/deletion can increase system memory and disk resource utilization for your Appian environment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2020

Tags: process models, application design, processes

[SP-3981] DRAFT KB-XXXX "Does not exist: Process" Error thrown in application server log, or when accessing a process instance

James Lee — Mon, 27 Apr 2020 21:42:21 GMT

Revision 5 posted to Appian Knowledge Base by James Lee on 4/27/2020 9:42:21 PM

Symptoms

When accessing a process instance via the Process Monitoring tab, the below error is thrown:

Load Error
Errors
This process diagram could not be opened due to the following errors.
Does not exist: Process

A similar error is printed in the application server stdOut log:

ERROR com.appiancorp.expr.server.reaction.smartservicebridge.SmartServiceBridgeReaction - Exception occurred during activation of ReactionFunction {key='sys.smartService.start-process-2', class='com.appiancorp.expr.server.reaction.smartservicebridge.PluginSmartServiceBridgeReaction'}
...
Caused by: com.appiancorp.suiteapi.process.exceptions.InvalidProcessException: Does not exist: Process

Cause

The process instance has been archived or deleted

Action

If the process has been archived, follow steps outlined in KB-1186 to unarchive the process instance.
Adjust archival/deletion thresholds in the Data Mangement tab to allow future process instances to be maintained for the desired amount of time after completion. Note increasing the length of time Process Instances are maintained before archival/deletion can increase system memory and disk resource utilization for your Appian environment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2020

Tags: process models, application design, processes

[SP-3981] DRAFT KB-XXXX "Does not exist: Process" Error thrown in application server log, or when accessing a process instance

James Lee — Mon, 27 Apr 2020 21:39:43 GMT

Revision 4 posted to Appian Knowledge Base by James Lee on 4/27/2020 9:39:43 PM

Symptoms

When accessing a process instance via the Process Monitoring tab, the below error is thrown:

Load Error
Errors
This process diagram could not be opened due to the following errors.
Does not exist: Process

A similar error is printed in the application server stdOut log:

ERROR com.appiancorp.expr.server.reaction.smartservicebridge.SmartServiceBridgeReaction - Exception occurred during activation of ReactionFunction {key='sys.smartService.start-process-2', class='com.appiancorp.expr.server.reaction.smartservicebridge.PluginSmartServiceBridgeReaction'}
...
Caused by: com.appiancorp.suiteapi.process.exceptions.InvalidProcessException: Does not exist: Process

Cause

The process instance has been archived or deleted

Action

If the process has been archived, follow steps outlined in KB-1186 to unarchive the process instance.
Adjust archival/deletion thresholds in the Data Mangement tab. Note increasing the length of time Process Instances are maintained before archiving/deleting can increase system memory and disk resource utilization for your Appian environment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2020

Tags: process models, application design, processes

[SP-3981] DRAFT KB-XXXX "Does not exist: Process" Error thrown in application server log, or when accessing a process instance

James Lee — Mon, 27 Apr 2020 21:31:57 GMT

Revision 3 posted to Appian Knowledge Base by James Lee on 4/27/2020 9:31:57 PM

Symptoms

When accessing a process instance via the Process Monitoring tab, the below error is thrown:

Load Error
Errors
This process diagram could not be opened due to the following errors.
Does not exist: Process

A similar error is printed in the application server stdOut log:

ERROR com.appiancorp.expr.server.reaction.smartservicebridge.SmartServiceBridgeReaction - Exception occurred during activation of ReactionFunction {key='sys.smartService.start-process-2', class='com.appiancorp.expr.server.reaction.smartservicebridge.PluginSmartServiceBridgeReaction'}
...
Caused by: com.appiancorp.suiteapi.process.exceptions.InvalidProcessException: Does not exist: Process

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been addressed via AN-XXXXX in Appian X.X Hotfix Package X.
This issue has been addressed via AN-XXXXX in the following hotfixes/versions:
- List each specific hotfix package/version in descending order by version.
This use case has been incorporated in Appian X.X Hotfix Package X.
This use case has been incorporated in the following versions/hotfixes:
- List each specific hotfix package/version in descending order by version.

Note: When listing hotfixes, add a hyperlink to the Hotfix documentation for that version.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

If no cause is known and this is not something Engineering can reproduce/needs to know about, then say “The root cause of this issue is currently unknown.” If you use that as your cause, then a valid action must be present.

Action

This section is required for this template and contains the steps to resolve the issue. If an issue in an article is solved by a hotfix and/or major version of Appian, use the following language to indicate that:

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is a product issue with Engineering that is open and a workaround for that issue exists, include it in the Action section until the fix is available. After the fix is made available, use that as a workaround instead.

Otherwise, the content in this section should wholly solve a customer’s issue without producing any undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Workaround

This section is optional and should only be used as an alternative action if there is a massive technical debt associated with performing the action in the above section for customers (such as upgrading). It can also be used if there is a solution to the issue in the article but is more inconvenient to implement or it causes other undesirable behavior and wouldn’t warrant being an action.

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all versions of Appian.
This article applies to Appian 7.11 and later.
This article applies to Appian 16.2 and earlier.
This article applies to Appian 7.11 and 16.1.
This article applies to Appian 16.1, 16.2, and 16.3.
This article applies to all versions of Appian from Appian 7.10 to Appian 16.2.
This article applies to all versions of Appian using JBoss EAP 6.4.9 as an application server and Internet Explorer 9 as a web browser.
This article applies to all versions of Appian Cloud.

Last Reviewed: Month YYYY

[SP-3981] DRAFT KB-XXXX "Does not exist: Process" Error thrown in application server log, or when accessing a process instance

James Lee — Mon, 27 Apr 2020 21:31:31 GMT

Revision 2 posted to Appian Knowledge Base by James Lee on 4/27/2020 9:31:31 PM

Symptoms

When accessing a process instance via the Process Monitoring tab, the below error is thrown:

Load Error

Errors

This process diagram could not be opened due to the following errors.

```
Does not exist: Process
```

A similar error is printed in the application server stdOut log:

ERROR com.appiancorp.expr.server.reaction.smartservicebridge.SmartServiceBridgeReaction - Exception occurred during activation of ReactionFunction {key='sys.smartService.start-process-2', class='com.appiancorp.expr.server.reaction.smartservicebridge.PluginSmartServiceBridgeReaction'}
...
Caused by: com.appiancorp.suiteapi.process.exceptions.InvalidProcessException: Does not exist: Process

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been addressed via AN-XXXXX in Appian X.X Hotfix Package X.
This issue has been addressed via AN-XXXXX in the following hotfixes/versions:
- List each specific hotfix package/version in descending order by version.
This use case has been incorporated in Appian X.X Hotfix Package X.
This use case has been incorporated in the following versions/hotfixes:
- List each specific hotfix package/version in descending order by version.

Note: When listing hotfixes, add a hyperlink to the Hotfix documentation for that version.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

Action

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Workaround

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all versions of Appian.
This article applies to Appian 7.11 and later.
This article applies to Appian 16.2 and earlier.
This article applies to Appian 7.11 and 16.1.
This article applies to Appian 16.1, 16.2, and 16.3.
This article applies to all versions of Appian from Appian 7.10 to Appian 16.2.
This article applies to all versions of Appian using JBoss EAP 6.4.9 as an application server and Internet Explorer 9 as a web browser.
This article applies to all versions of Appian Cloud.

Last Reviewed: Month YYYY

DRAFT KB-XXXX "Does not exist: Process" Error thrown in application server log, or when accessing a process instance

James Lee — Mon, 27 Apr 2020 21:20:54 GMT

Revision 1 posted to Appian Knowledge Base by James Lee on 4/27/2020 9:20:54 PM

Symptoms

This section is required for this template. All symptoms of the issue, including relevant screenshots and log lines, should be included here. The symptoms should be as descriptive as possible.

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been addressed via AN-XXXXX in Appian X.X Hotfix Package X.
This issue has been addressed via AN-XXXXX in the following hotfixes/versions:
- List each specific hotfix package/version in descending order by version.
This use case has been incorporated in Appian X.X Hotfix Package X.
This use case has been incorporated in the following versions/hotfixes:
- List each specific hotfix package/version in descending order by version.

Note: When listing hotfixes, add a hyperlink to the Hotfix documentation for that version.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

Action

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Workaround

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all versions of Appian.
This article applies to Appian 7.11 and later.
This article applies to Appian 16.2 and earlier.
This article applies to Appian 7.11 and 16.1.
This article applies to Appian 16.1, 16.2, and 16.3.
This article applies to all versions of Appian from Appian 7.10 to Appian 16.2.
This article applies to all versions of Appian using JBoss EAP 6.4.9 as an application server and Internet Explorer 9 as a web browser.
This article applies to all versions of Appian Cloud.

Last Reviewed: Month YYYY