Access Profiles created via API are not searchable via API

When I create an access-profile via the API the following happens:

  • Access Profile created successfully
  • Access Profile is visible in the UI
  • Access Profile returns in a call to the /access-profiles endpoint
    *Issues
  • Access Profile is not searchable
  • Since its not searchable, its not available in the ServiceNow catalog

*Odd findings

  • Cannot delete the access profile from the UI, says “Access Profile Already Deleted”
  • Can delete access profile from the /access-profiles endpoint

Comparing /access-profiles results for 2 entries, “Allscripts” created via API and “Allscripts1” created by the UI, they look identical.

Anyone else run into this?

Hi Jason,

When you say it is not “searchable”, do you mean you can’t find it in the Search UI? How long between when you created the access profile and when you tried to search for it? There is a latency in search because objects have to be loaded into the search database before they can be found. The time this takes can depend on system load.

This issue has been brought to engineering and they are investigating a fix.

I have noticed this same behaviour, but I think all you need to do is wait. I have tried calling the API for access-profiles in v2, v3 and BETA and usually the (new) access profile is missing from one of these requests which I find quite odd. I would think they all call the same db?