SailPoint IdentityIQ 8.1 → 8.3p5 (issue started after upgrade)
Please share any other relevant files that may be required (for example, logs).
INFO RequestProcessor … Host:idmprdtsk02: 14 threads running, 0 threads queued
WARN BundleProfileRelationServiceSynchronizer … Maximum backlog threshold reached for BundleProfileRelationService, the backlog amount of 1503331 exceeds the maximum threshold of 100000
Share all details about your problem, including any error messages you may have received.
Hello,
After upgrading from 8.1 to 8.3p5, the BundleProfileRelation table (bundle_profile_relation / BundleProfileRelation) keeps growing because records are not being cleaned up. The table is now > 4 million rows. Currently we do not observe a major performance impact, but debug pages are no longer opening, and we are concerned the growth/backlog will eventually cause performance or stability issues. Question:
Is this a known issue in 8.3p5 (especially post-upgrade)?
Is it safe/supported to TRUNCATE the BundleProfileRelation table directly in DB? If not, what is the supported cleanup/rebuild procedure?
Recommended fix/workaround (task/command/config/patch/e-fix) to reduce backlog and prevent regrowth.
@meltemcan I don’t think you should truncate the table. Truncating can lead to data inconsistency in role reporting and may cause errors in other IIQ module that expect these relationships to exist. While it might provide temporary relief, the synchronizer will likely just start rebuilding it (and potentially re-encountering the loop/error) immediately.
For the time being, you can try disabling it in all servers. To do this,:
Go to the Gear Icon → Administrator Console.
Navigate to Environment.
Click the gear icon next to your task server
In the Services tab, find BundleProfileRelation and toggle it OFF.
This will stop the synchronizer and reduce the resource load, allowing debug pages to open.
Post this, you might want to review your relationship. Possibly open a support ticket to take Sailpoint team’s guidance.
Note: Found a fix?Help the community by marking the comment as solution. Feel free to react(,, etc.)with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.
