What problem are you observing?
Sporadically we’re seeing that new Access Profiles cannot be immediately be added to an Application. The request fails with HTTP 404
and a message of "The server did not find a current representation for the target resource."
The behavior is the same whether using the API or UI to create the Access Profile and add to an Application.
What is the correct behavior?
If an Access Profile is successfully created, has an ID and can be viewed in the UI, you should be able to add it to an Application without error.
What product feature is this related to?
Specifically this is occurring when using the Beta or V2024 PATCH Apps API and adding a newly created Access Profile.
What are the steps to reproduce the issue?
This typically happens when these steps are run in code (i.e. very quickly, sequentially), however, this sometimes can take minutes or even longer for step 3 to succeed due to this bug.
- Create an Application
- Create and Access Profile
- Add Access Profile to Application
Do you have any other information about your environment that may help?
It appears that the Apps API is relying on Search to validate Access Profiles to be added. When experiencing this error, the problem Access Profile cannot be found via Search, even though it be found using the Access Profiles API or viewed in the UI. This dependency on search indexing is likely causing the issue.