Resolve duplicate patch upgrades running on secondary nodesIssue After a successful upgrade from one version to another on your primary node, a duplicate upgrade job starts on a secondary node. The Upgrade Monitor displays the status of the second upgrade as "In Progress" but does not complete. Release All supported releases Cause This issue occurs when the System ID field in the [sys_trigger] table is manually set to NULL after the first upgrade completes. When this happens, a secondary node detects an incomplete trigger and attempts to run the upgrade again. Resolution Follow these steps to resolve the duplicate upgrade: Verify that no upgrade jobs are currently running on any node. Open the Scheduled Jobs [sys_trigger] table by navigating to System Administration > Scheduled Jobs or visiting (your instance URL)/sys_trigger.list.Check the State field for any jobs with status "Running" or "Queued."If running jobs exist, wait for them to complete before proceeding. Delete the [sys_upgrade_history] record created for the second (duplicate) upgrade. Open the Upgrade History table by navigating to System Administration > Upgrade History or visiting (your instance URL)/sys_upgrade_history.list.Locate the upgrade history record for the duplicate upgrade (the second one that did not complete).Select the record and use the delete function to remove it.Note: Some instances may require a change request for this deletion. Check your organization's change management policies before deleting. Clear the stuck upgrade status in the Upgrade Monitor. Navigate to System Administration > Upgrade > Upgrade Monitor or visit (your instance URL)/upgrade_monitor.do.Select the Fix Upgrade Jobs link to reset the upgrade job status.Verify that the Upgrade Monitor no longer displays the stuck upgrade status.