# ISC UI fails again with newly introduced functionality for partial admin user levels **URL:** \ **Category:** Bugs\ **Tags:** fixed, ui, applications, sailpoint-identity-security, sources\ **Created:** [November 5, 2024, 10:08am UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668 "2024-11-05T10:08:19Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![angelo\_mekenkamp](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/angelo_mekenkamp/32/3386_2.png) [@angelo\_mekenkamp](https://developer.sailpoint.com/discuss/u/angelo_mekenkamp)\ **Post date:** [November 5, 2024, 10:08am UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668/1 "2024-11-05T10:08:19Z")
Hi all, 🙂 This error occurs in our production environment. We have an identity with these user levels: Role `Sub-admin`, `Source Sub-admin`. When this identity goes to the sources page in the UI, it will show this error: ![image](https://global.discourse-cdn.com/sailpoint/original/3X/2/d/2d1a614e1ca323d9eceb28bfe04ce4ef2b7ad932.png) This occurs when the UI tries to call this API endpoint: `beta/discovered-applications` The issue occurs with `sub-source admin`, but also with `source admin`, not with `org_admin` I am noticing a pattern of UI errors in the UI in production for users that have some admin rights, but not full on `ORG_ADMIN`. I believe SailPoint should check if or they are actually testing UI changes on all user levels prior to releasing it, or how/when they are doing it, because that seems to be the crux of this pattern of bugs. Kind regards, Angelo ---
**Author:** ![adamian](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@adamian](https://developer.sailpoint.com/discuss/u/adamian)\ **Post date:** [November 6, 2024, 10:53am UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668/2 "2024-11-06T10:53:01Z")
> [@angelo\_mekenkamp](#): > > I believe SailPoint should check if or they are actually testing UI changes on all user levels prior to releasing it, or how/when they are doing it, because that seems to be the crux of this pattern of bugs. Hi Angelo, do you know if SailPoint released some videos / blog posts with insights on how their engineering team is working and what tools they may be using? Something along these lines: [GitHub - kilimchoi/engineering-blogs: A curated list of engineering blogs](https://github.com/kilimchoi/engineering-blogs) I am highly interested in how they perform their testing (unit tests, integration, regression, end to end etc), write the specifications, manage bugs etc. ---
**Author:** ![angelo\_mekenkamp](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/angelo_mekenkamp/32/3386_2.png) [@angelo\_mekenkamp](https://developer.sailpoint.com/discuss/u/angelo_mekenkamp)\ **Post date:** [November 6, 2024, 11:01am UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668/3 "2024-11-06T11:01:56Z")
> [@adamian](#): > > Hi Angelo, do you know if SailPoint released some videos / blog posts with insights on how their engineering team is working and what tools they may be using? This is a black box to me, but given the amount of bugs that manage to make its way to our production tenants, I would argue that whatever process they have or which tools they use, this should be reviewed. ---
**Author:** ![angelo\_mekenkamp](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/angelo_mekenkamp/32/3386_2.png) [@angelo\_mekenkamp](https://developer.sailpoint.com/discuss/u/angelo_mekenkamp)\ **Post date:** [November 21, 2024, 10:59am UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668/4 "2024-11-21T10:59:43Z")
Update from SailPoint Support: > [@SailPoint Support](#): > > Can you please validate the issue once again at your end? > I can see a fix is pushed by the engineering team and I am unable to replicate on my test setup. Just checked, issue is still there. ---
**Author:** ![adamian](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@adamian](https://developer.sailpoint.com/discuss/u/adamian)\ **Post date:** [November 22, 2024, 9:42am UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668/5 "2024-11-22T09:42:00Z")
> I can see a fix is pushed by the engineering team and I am unable to replicate on my test setup. What does “a fix is pushed” mean? From my current understanding they deploy some bug fixes over weeks, and we have no official way to know when something is deployed on our tenants, so did they push this fix on your tenant as well? ---
**Author:** ![angelo\_mekenkamp](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/angelo_mekenkamp/32/3386_2.png) [@angelo\_mekenkamp](https://developer.sailpoint.com/discuss/u/angelo_mekenkamp)\ **Post date:** [November 22, 2024, 9:48am UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668/6 "2024-11-22T09:48:47Z")
> [@adamian](#): > > What does “a fix is pushed” mean? Do you know the answer to this one @colin_mckibben? ---
**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Post date:** [November 22, 2024, 2:07pm UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668/7 "2024-11-22T14:07:52Z")
Code changes aren’t typically deployed to all tenants at once. We do phased rollouts to catch issues early and ensure a code change doesn’t have widespread impacts. A “fix is pushed” might mean that your tenant has the fix, but other tenants won’t get it for days/weeks. ---
**Author:** ![angelo\_mekenkamp](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/angelo_mekenkamp/32/3386_2.png) [@angelo\_mekenkamp](https://developer.sailpoint.com/discuss/u/angelo_mekenkamp)\ **Post date:** [November 22, 2024, 2:33pm UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668/8 "2024-11-22T14:33:22Z")
Makes a lot of sense @colin_mckibben! However, if I am the one creating a support ticket to SailPoint Support, and they reply to me saying the fix has been deployed and ask me to test it, I do expect that it is at least already pushed to the tenant I mentioned when creating the ticket. Is there a way for SailPoint Support to see if this is pushed to specifically my tenant already and only then ask us to test it? ---
**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Post date:** [November 22, 2024, 2:43pm UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668/9 "2024-11-22T14:43:12Z")
They should be able to ask engineering for a list of tenants/regions where it was deployed. If they give you a generic “it should have been deployed”, try asking them if your tenant is included in the deployment. ---
**Author:** ![angelo\_mekenkamp](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/angelo_mekenkamp/32/3386_2.png) [@angelo\_mekenkamp](https://developer.sailpoint.com/discuss/u/angelo_mekenkamp)\ **Post date:** [November 22, 2024, 3:21pm UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668/10 "2024-11-22T15:21:52Z")
Alright will do! I do think however that it would be good if this is part of their training to confirm this first. As I think this process: 1. Engineering team says fix is pushed to Support 2. Support asks Engineering team if our tenant is included in the deployment already, until it actually has. 3. Support tells us the fix is deployed and asks us to test it. 4. We test, based on actual changes made Makes more sense then this process: 1. Engineering team says fix is pushed to Support. 2. Support tells us the fix is deployed and asks us to test it. 3. We learn from Colin to first ask Support if this deployment actually included our tenant 4. Support asks Engineering team if our tenant is actually included in the deployment already until it has. 5. Support tells us the fix is deployed and asks us to test it. 6. We test, based on actual changes made ---
**Author:** ![angelo\_mekenkamp](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/angelo_mekenkamp/32/3386_2.png) [@angelo\_mekenkamp](https://developer.sailpoint.com/discuss/u/angelo_mekenkamp)\ **Post date:** [December 4, 2024, 11:15am UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668/11 "2024-12-04T11:15:57Z")
Update from SailPoint Support: 13 hours ago, the engineering team was able to fix the bug. SailPoint Support will check if this fix has been deployed successfully. ---
**Author:** ![angelo\_mekenkamp](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/angelo_mekenkamp/32/3386_2.png) [@angelo\_mekenkamp](https://developer.sailpoint.com/discuss/u/angelo_mekenkamp)\ **Post date:** [December 6, 2024, 2:34pm UTC](https://developer.sailpoint.com/discuss/t/isc-ui-fails-again-with-newly-introduced-functionality-for-partial-admin-user-levels/88668/12 "2024-12-06T14:34:48Z")
Received a new update from SailPoint Support today: > [@SailPoint Support](#): > > Hello Angelo, > > This issue seems to be fixed in Staging and Production. Please verify in your environment. Just checked, issue is not visible anymore. Note that this bug was reported a month ago, where 16 days ago we got the first (wrong) claim that the fix was pushed and only now we received a correct claim that the issue was fixed. [@community\_moderators](https://developer.sailpoint.com/discuss/groups/community_moderators), please apply the `fixed` tag here, as I am not authorized to do this myself. Kind regards, Angelo