RECONNECT REQUIRED
Troubleshoot reconnect required responses from the Ovok API.
HTTP 409. Stable Problem Details type: https://docs.ovok.com/errors/reconnect-required.
What this means
The provider no longer accepts this wearable connection, for example because the patient removed the app's access in their provider account or the provider revoked the grant. Ovok stops syncing it until the patient connects again. Clients should branch on type and status, not on human-readable detail text.
Troubleshooting
Ask the patient to connect the provider again with POST /v1/wearables/connections/<provider>/authorize; a new connection clears the flag. Until then, GET /v1/wearables/connections shows reconnectRequired: true. Syncing again without reconnecting returns the same error. Compare the request with the relevant endpoint's documentation and confirm the authenticated project and environment. Record the request path and traceId before escalating; the identifier lets an administrator find server-side context without sharing credentials or patient data.
Related endpoint guidance
Use these pages to check the route, project settings, and request requirements associated with this error:
Retry safely
Correct the request, configuration, access or project state described above before retrying. Repeating an unchanged request will normally return the same error; for writes, check whether the first attempt changed state before sending it again. Follow endpoint-specific idempotency and concurrency guidance. Do not retry in a tight loop or use a broader permission or project setting to bypass the check.
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 sensitive patient data from the report. The Error responses guide explains the response fields, while the machine-code registry lists every endpoint-specific type audited for this release.
Last updated on