Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
connect-api logs fill with "(E) 400: Invalid Item UUID" errors when running connect-api 1.5.6 / connect-sync 1.5.6 alongside the onePassword operator 1.5.0. Syncing appears affected.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
This was fixed in Connect 1.7. Users who upgraded from 1.5.6 to 1.7.2 reported the errors were gone, and the maintainers closed the issue as fixed in 1.7. Upgrade both connect-api and connect-sync to 1.7.x.
Source: https://github.com/1Password/connect-helm-charts/issues/45
Source: https://github.com/1Password/connect-helm-charts/issues/45
Shows how to fix 1Password Connect 400 Invalid Item UUID errors in connect-api logs. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix 1Password Connect 400 Invalid Item UUID errors in connect-api logs. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes the Okta failure "access review agent retried Okta users list API on 400 invalid cursor: infinite retry loop" by acting on the exact message, proving the fix on one item, then rerunning and reconciling counts.