op 2.3 via Connect broken

I've looked a bit into the code responsible for this, and have confirmed that this error can be returned in two cases:

• the section cannot be properly identified
• the field cannot be properly identified

In order to continue diagnosing this, can you please take another look at your item's json and let us know if there is anything that appears unusual about the section/the field that this error happens for?

In particular, I am interested whether the field ID and the section ID (as they can be seen in the item's json format) are properly formatted: i.e. strings made out of 26 characters (lowercase letters and digits). My hunch is that there may be something off with the validation that the CLI performs when passing queries to Connect, when looking up sections/fields.

Looking forward to hearing from you.

Best,
Horia