Escalation Workflows randomly fail to trigger in RSA Identity Governance & Lifecycle
Originally Published: 2020-07-13
Article Number
Applies To
RSA Version/Condition: All
Issue
The following error is logged to the WorkPoint.log file:
2020-04-27 15:11:21,730 [pool-16-thread-1] INFO com.workpoint.server.ServerProperties - ServerProperties.setProperty() invoked for property= calculated.db.offset.millis.jdbc/avdb, value=-22136
2020-04-27 15:11:21,730 [pool-16-thread-1] WARN com.workpoint.server.ConnectContext - The time difference between the database server for DSN= jdbc/avdb and this machine has changed by 44270ms since last computed. This may be a sign of clock drift on one of the machines, which can lead to unexpected results in Workpoint.
2020-04-27 15:11:21,730 [pool-16-thread-1] WARN com.workpoint.server.ConnectContext - The time difference between the database server for DSN= jdbc/avdb and this machine has changed by 44270ms since last computed. This may be a sign of clock drift on one of the machines, which can lead to unexpected results in Workpoint.
Please refer to RSA Knowledge Base Article 00003027 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the WorkPoint.log file for your specific deployment.The WorkPoint.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)
Cause
Resolution
Related Articles
Review escalation workflows do not trigger if review is set to Hold by an escalation workflow after due date in RSA Identi… Number of Views Review escalation workflows sometimes do not trigger in RSA Identity Governance & Lifecycle Number of Views Unable to save Application Role mapping in Role Collector in RSA Identity Governance & Lifecycle Number of Views Role import does not include Available For Request set to No Number of Views Running sdcompress; error: 'TRIGGER ERROR' Number of Views
Trending Articles
Don't see what you're looking for?
