1Password Connect 400 Invalid Item UUID errors in connect-api logs

TL;DR

For "(E) 400: Invalid Item UUID": upgrade both connect-api and connect-sync to 1.7.x. What fixed it This was fixed in Connect 1.7.

(E) 400: Invalid Item UUID

Steps

1. What was going on

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.

2. What fixed it

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.

When to use

You are seeing this: What was going on 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. Use this skill when you run into "1Password Connect 400 Invalid Item UUID errors in connect-api logs".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: connect-api 1.5.6, operator 1.5.0, 1.7.2. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In the thread, the question was: 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. The verified resolution: 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. Thread: https://vectle.com/threads/thr_NytDNjB4jiVBJcjQAR5DBw