You might be unable to start a new workflow instance for a business object even though an existing workflow instance cannot be found. The problem sometimes occurs due to an out-of-sync condition between the workflow_registry table in the SAS Risk Governance Framework database and the workflow tables in the SAS^® Shared Services database.

The workflow_registry table might contain a reference to a workflow instance for a business object, but the workflow instance no longer exists in the SAS Shared Services database. This problem could occur if you back up and restore the SAS Risk Governance Framework database but fail to back up and restore the SAS Shared Services database.

A new option for the removeWorkflowInstances command in the SAS Risk Governance Framework enables you to remove workflow instances from the workflow registry. The option removes only workflow instances that no longer exist in the SAS Shared Services database. To remove orphaned workflow instances from the workflow registry, specify the r option, as shown in the example below:

You can specify the r option with the o option to remove orphaned workflow instances from the workflow registry and from the SAS Shared Services database. The orphaned workflow instances that are removed from the SAS Shared Services database are associated with business objects that no longer exist in the SAS Risk Governance Framework database. When the SAS Shared Services database contains orphaned workflow instances, you see warning messages in the SASRiskGovernanceFrameworkMidTier.log file similar to the following:

To remove orphaned workflow instances from the workflow registry and from the SAS Shared Services database, specify the r option and the o option, as shown below:

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Risk Governance Framework 7.4 is available at: