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 174Number of Views Accessing the raw data tabs for collector runs is very slow in RSA Identity Governance & Lifecycle 28Number of Views Cancel all Scheduled Occurrences of a Log Archive Job 17Number of Views
Trending Articles
Artifacts to gather in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle RSA MFA Agent for UNIX Platform Support Matrix
Don't see what you're looking for?