PUSH_DEVICE_NOT_FOUND
Push device not found: what the PUSH_DEVICE_NOT_FOUND error means and how to fix it.
HTTP 404. Problem type: https://docs.ovok.com/errors/push-device-not-found.
What this means
You have no push device with this id. A device of another person, or of another project, answers the same way, so this does not tell you whether the id exists elsewhere.
Troubleshooting
- List your devices with
GET /v1/push/devicesand take theidfrom there. - Register the device's token again with
POST /v1/push/devicesto get its id. Registering the same token twice is safe. - If someone else signed in on the device since, the device moved to them and is no longer yours.
Retry safely
Retrying the same id does not help. The device may already be gone, which is where a removal would leave it.
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