Identity Profile is pointing to a deleted source → backend inconsistency → requires support fix

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

Hi,

I’m facing a data integrity issue while accessing Identity Profiles.

Error:
500.2.1 Data integrity issue
Authoritative Source referenced by Identity Profile “akshat” not found

This issue is occurring both in UI and via API (Postman), and I’m unable to view or manage Identity Profiles.

It seems like the profile is referencing a source that no longer exists.

Has anyone faced a similar issue? Is there any workaround from the UI/API, or does this require SailPoint Support intervention?

Thanks!

2

Hi @Gxurav713

How the source got deleted when the Identity Profile is linked with the source ? Usually, It wont let you delete the source if it is linked with Identity Profile.

You can reach out to SailPoint support for this issue.

3

Hi,

Yes, that’s what I also thought — ideally the system shouldn’t allow deletion if the source is still linked.

That’s why this behavior was a bit confusing. It seems like there might be some stale or broken reference in the backend.

I’ll go ahead and raise this with SailPoint Support to get it checked.

Thanks for your input!

4

Hi Gouravraj,

Normally, ISC won’t allow a source to be deleted while it’s still referenced by an Identity Profile. The expected sequence is: reset the source → delete the Identity Profile → then delete the source. The UI enforces this.

That said, there are cases where objects appear deleted in the UI but still exist in the backend, which can lead to this kind of data integrity issue. This seems similar to what you’re running into.

I came across a few threads with the same error, where the workaround was to delete the Identity Profile directly using its ID. The suggested (and marked as a solution) approach was:

***“Fetch the Identity Profile ID causing the issue. If Beta or v3 APIs don’t return it, try cc APIs (if still available). Then use that ID to delete the Identity Profile via the v3 API.”

Plz check this below thread :backhand_index_pointing_down:

Reference: Error While entering identity profiles page

If the API approach doesn’t work, this would likely need SailPoint Support to clean it up from the backend.

5

Hi @Gxurav713 ,
If you dont have that source exists in your tenant, go to that specific identity profile and remove that source name or select another source and configure mappings and then do the apply changes.
Thanks

6

Hi,

Thanks for the detailed explanation, this really helps.

The point about backend references still existing even after deletion makes sense — that seems to match what I’m seeing.

I’ll try fetching the Identity Profile ID and see if I’m able to delete it via API. If that doesn’t work, I’ll proceed with raising a support case.

Appreciate you sharing the reference as well!

7

Hi,

Thanks for the suggestion.

In my case, I’m not able to access the Identity Profile itself — the error is coming up as soon as I open the Identity Profile tab, so I’m unable to update or remove the source from UI.

It seems like the profile might still exist in the backend but is not accessible from the UI.

I’ll try the API approach suggested earlier, and if that doesn’t work, I’ll raise it with SailPoint Support.

Thanks again!

8

Yes, please try to remove the identity profile using api.

9

@Gxurav713

Have you tried deleting the Identity Profile with the help of API?

If it does not work then you cn reach out to Sailpoint support.

10

Sounds good, please give that a try & let me know how it goes. I am interested to see what ends up resolving it.

11

Hi,

I already tried checking via API, but I’m not able to see that Identity Profile in the response at all.

It seems like it’s not accessible through the API either, which makes me think it might be a backend reference issue.

I’ll go ahead and raise this with SailPoint Support.

Thanks for the suggestion!

12

Hi,

I already tried checking via API, but I’m not able to see that Identity Profile in the response at all.

It seems like it’s not accessible through the API either, which makes me think it might be a backend reference issue.

I’ll go ahead and raise this with SailPoint Support.

Thanks for the suggestion!

13

Hi,

I gave it a try, but I’m not able to retrieve or delete the Identity Profile via API.

I’ve raised this with SailPoint Support now and will share the update once I hear back.

Thanks!

14

Then Sailpoint support is the only option.

15

Thanks for the update. Please do share what Support comes back with. I am interested to see how this gets resolved & what the root cause turns out to be.

Just to confirm my understanding, the source was deleted but the Identity Profile itself was not deleted, right? It still exists but is not accessible via the UI/API.

You also mentioned you were not able to retrieve the Identity Profile ID via API. Ideally, if the object still exists in the backend, the API should return it even if the UI is failing.

If you don’t mind sharing, how did you try to fetch the Identity Profile ID?

For reference, these are the APIs I had in mind:

Trying to understand whether this is a true backend inconsistency where the object is not retrievable at all, or more of a UI or API surface limitation.

16

Hi,

Yes, that’s what it looks like now.

Since it’s not visible via UI or API, it seems like a backend issue. I’ve already raised a case with SailPoint Support and will wait for their update.

Thanks!

17

Hi,

Thanks for the detailed response.

Yes, that’s my understanding as well — it looks like the source might have been deleted, but the Identity Profile is still being referenced somewhere in the backend, even though it’s not accessible via UI or API.

For API, I tried using the standard v3 List Identity Profiles endpoint, but the profile is not returned in the response at all. Because of that, I’m not able to get the ID to attempt deletion.

So it seems like the object is neither visible in UI nor retrievable via API, which points more towards a backend inconsistency.

I’ve raised this with SailPoint Support and will share the update once I hear back.

Thanks again for your insights!