Active Request Conditions that were active on deleted applications are left behind as 'phantom' or 'zombie' request conditions, as they cannot be edited via the Applications > Applications > [[application name]] > Access Requests menu.

• Okta Identity Governance (OIG)
• Resource Centric Access Requests (RCAR)

This issue is caused by deleting an application that has an active, associated request condition in the Applications > Applications > [[application name]] > Access Requests menu prior to disabling the request condition.

The below steps to resolve this can be performed with a tool like Postman or with Workflows. The okta.accessRequests.condition.manage scope is required as part of the authentication in whichever tool is used.

1. Retrieve the application ID for the deleted app. The best way to accomplish this is to search the Okta System Log for the application.lifecycle.delete event that corresponds to the app in question and save that ID.
2. Open this documentation regarding the RCAR API. For more information, please see Managing Request Conditions using APIs documentation. 
3. Use the List all Request Condition endpoint from the above document to list all the conditions associated with the deleted application and use the application ID from step 1.
4. In the payload returned from step 3, find the active request condition that is still showing up and retrieve its ID.
5. Use the Deactivate the request condition endpoint to deactivate the access request in question.
6. (Optional) Use the Delete a request condition endpoint to delete the access request condition.

Related References

• Managing Request Conditions using APIs