Health Check Error: Invalid SugarBPM Serialization

Overview

The Health Check wizard must be run when upgrading in order to evaluate whether your instance is suitable for upgrade. The Health Check wizard detects a variety of issues that may affect your ability to upgrade. This article will cover how to resolve an "Invalid SugarBPM Serialization" error reported by the health check.

Note: This error was titled "Invalid Advanced Workflow Serialization" prior to Sugar 9.x.

Symptoms

This error generates an output similar to the following in health check:

This error indicates that you have an invalid process-related record in your instance.

Resolution

If any data in the SugarBPM (pmse_*) tables that would contain serialized data but that data cannot be unserialized, then the Health Check wizard will report this error. The issue will need to be fixed before proceeding with the upgrade.

The generated error message will help determine the contents of the file causing the health check error. We will use the following error message as an example:

1 invalid serialization(s) in the pro_locked_variables column of the pmse_bpm_process_definition table: Serialized with ID '1000099f-5ae7-e53c-c6fa-55b6e0a372c6'

This example provides the table (pmse_bpm_process_definition) and field (pro_locked_variables) where the corrupt data occurs as well as the ID (1000099f-5ae7-e53c-c6fa-55b6e0a372c6) for the specific record within that table. To address this error, navigate to the affected record in Sugar and remove the record in order to continue with the upgrade. Please note that any invalid SugarBPM records can be re-created in the upgraded instance.

Once the necessary changes have been made, please navigate to Admin > Repair and perform a "Quick Repair and Rebuild" to ensure that the changes are synced between the application and database.

Perform the health check again to confirm that the error is no longer reported.