Contributed by Andrzej Adamczyk
The DeploymentManagerAgentScheduler job scheduler cannot trace the job and cannot find job information.
The problem was reported for the following scenarios.
The PDC monitoring report for the environment in which you experience this problem does not find the Dynamic System Setting (DSS), job/schedule/lock/method.
You cannot deploy code in a production environment and, while checking environment health, you see the error DeploymentManagerAgentScheduler job scheduler has not executed in last 60 minutes.
Unable to trace the job. Job info could not be found.
DeploymentManagerAgentScheduler job scheduler has not executed in last 60 minutes.
Client misunderstanding, configuration error
Suspected issue with the way the lock was obtained using Hazelcast client-server mode
Suspected documentation gap
The problem was reported for Pega Platform™ 8.8.3 in a Pega Cloud® services 3.0 environment.
To restore the DeploymentManagerAgentScheduler to an active state, set the following DSS:
Ruleset = Pega-RulesEngine
Purpose = job/schedule/lock/method
Value = persistence
This DSS changes the job scheduler locking mechanism, not the job scheduler behavior. It uses the database instead of Hazelcast because of the suspected issue with the way that the lock is obtained using Hazelcast client-server mode.