Issue

After upgrading to Pega Infinity™ 26 or later versions, environments show a Disconnected status on the Pega Diagnostic Center (PDC) homepage when no connectivity issues exist. 

Root cause

Beginning with Pega Infinity 26, PegaAESRemote agents were migrated to job schedulers. In some upgraded environments, the PegaAESRemote application is not automatically added to the System Runtime Context. As a result, the job schedulers responsible for communicating with PDC do not run, causing PDC to report the environment as disconnected. 

Solution

1. Log in to the affected environment with the Disconnected status.

2. Navigate to Records > Application Definition > Application.

3. Search for and open the PegaAESRemote application rule.

4. Click Save without making any changes.

5. If message signing is enabled, navigate to Configure > System > Settings > Pega Diagnostic Center. Turn off the toggle for PDC accepts only digitally signed messages and then turn it back on.

Saving the application Rule updates the System Runtime Context and adds PegaAESRemote to the application stack.

Verifying the environment status

1. Navigate to Configure > System > General > System Runtime Context.

2. Verify that you can see PegaAESRemote in the application stack.

3. Wait approximately 15 minutes for the job schedulers to resume sending data to PDC.

4. In the PDC home page, click Status Refresh.

5. Verify that the environment status changes from Disconnected to Connected.