POLICY_NOT_IN_PROJECT

Access policy in another project: what the POLICY_NOT_IN_PROJECT error means and how to fix it.

HTTP 403. Problem type: https://docs.ovok.com/errors/policy-not-in-project.

What this means

The id names an access policy that exists but belongs to another project, such as a project yours links to. /v1/access-policies and the access policy tools manage only the policies of the caller's own project. Nothing was changed.

Troubleshooting

  1. List this project's policies with GET /v1/access-policies or list_access_policies and take the id from there.
  2. To change a policy of another project, sign in to that project and change it there.

Retry safely

Retry with an id from this project. An unchanged call returns the same error. Nothing was changed.

If the problem persists

Share the HTTP status, problem type, request path, response timestamp and traceId with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The Error responses guide explains the response fields, and the machine-code registry lists every endpoint-specific type.

Last updated on

On this page