- RSA Identity Governance & Lifecycle 7.5.0
- SecurID Governance & Lifecycle 7.5.2
When one of the applications in a Multi-App Collector, Multi-App Account Collector (MAADC) or Multi-App Entitlement Collector (MAEDC), has no data AND the Multi-App Collector configuration option "If no data collected for an application, REMOVE its previously collected information" is enabled, then the entire Multi-App Collection fails due to the Circuit Breaker.
The collector status shows as:
Aborted (Circuit Breaker)
This issue is resolved in the following patches which adds a new feature to control the behavior of the Circuit Breaker for Multi-App Collectors.
The issue was fixed for Multi-App Entitlement Collectors in:
- RSA Identity Governance & Lifecycle 7.5.0 P08
- SecurID Governance & Lifecycle 7.5.2 P04
The issue was fixed for Multi-App Account Collectors in:
- RSA Identity Governance & Lifecycle 7.5.0 P09
- RSA Governance & Lifecycle 7.5.2 P05
If you want to modify the behavior, set the parameter "circuitBreakeFailureForMultiappCollectorIfAnyMissingApps" in T_SYSTEM_SETTINGS table using the procedure listed below. This parameter can be set to one of the following values:
- yes - default value. Circuit Breaker will trip when any application collects no data.
- no - Circuit Breaker is not tripped, and Data Pre-processing is completed.
Steps to verify the current setting of "circuitBreakeFailureForMultiappCollectorIfAnyMissingApps" and changing its value to control the behavior of the Circuit Breaker for Multi-App Collectors:
- Login as oracle user on the Oracle Database host.
- Run sqlplus as avuser.
- Verify the current value set for the parameter (the result will show the value 'yes' as the default):
select * from t_system_settings where parameter='circuitBreakeFailureForMultiappCollectorIfAnyMissingApps'; - Update the parameter to change the behavior of the Circuit Breaker for Multi-App Collectors (example showing how to set the value to 'no'):
update t_system_settings set value='no' where parameter='circuitBreakeFailureForMultiappCollectorIfAnyMissingApps'; commit; - Verify the current value set for the parameter (the result should show the changed value 'no' for the parameter):
select * from t_system_settings where parameter='circuitBreakeFailureForMultiappCollectorIfAnyMissingApps'; - Exit sqlplus and run the Multi-App Collectors to observe the changed behavior.
Related Articles
How to configure a JSON response in AFX connector capabilities to parse single or multi-valued responses in RSA Identity G… 60Number of Views How a Multi-App Entitlement Collector (MAEDC) resolves entitlement relationships with accounts and groups collected by a M… 142Number of Views 'Multi App Collector : 'Admin' privilege does not allow editing of the collector definition as expected in RSA Identity Go… 25Number of Views Multi-App Entitlement Data Collector (MAEDC) fails with ORA-30926 if two MAEDCs overlap in Application Name and Internal I… 55Number of Views Collection is stuck in the data collection phase in RSA Identity Governance & Lifecycle 6.9.1 573Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026) Supported On-Demand Authentication (ODA) SMS providers for use with RSA Authentication Manager 8.x Deploying RSA Authenticator 6.2.2 for Windows Using DISM