Cannot avoid circuit breaker abort for scheduled Identity Data Collector (IDC) collections in RSA Identity Governance & Lifecycle
Originally Published: 2018-04-30
Last Modified: 2023-11-30
Article Number
Applies To
RSA Version/Condition: All
Issue
Cause
(number of items added/changed/deleted) / (number of items in total).
For example,
- If there were 200 accounts last time, and this time 150 of them are unchanged, but 50 have been deleted, you end up with 50/150, or 33% change.
- If there were 200 accounts last time, and this time 200 of them have been deleted, leaving 0, you end up with 200/0, which is not a valid equation.
Resolution
Related Articles
Edit a Scheduled Report Job 8Number of Views Schedule a Cleanup Job 86Number of Views Scheduled custom reports are intermittently failing and generating blank reports in RSA Identity Governance & Lifecycle 175Number of Views Delete a Scheduled Report Job 10Number of Views Accessing the raw data tabs for collector runs is very slow in RSA Identity Governance & Lifecycle 28Number of Views
Trending Articles
Deploy an Identity Router Virtual Machine in Microsoft Azure How to Replace the Web Server Certificate for the RSA Identity Governance & Lifecycle Web Console How to download the RSA Authentication Manager Console Root Certificate in DER format How to Change the Token Lifetime Extension Window in Authentication Manager Using rsautil AFX Server and Remote Collection Agents fail to start after updating Java to version 1.8u241 (1.8.0_241) / 1.7u251 (1.7.0_…
Don't see what you're looking for?