Issue with Sanity AI Assist not working, possible problem with schema validation error.

Hey y’all! The Sanity AI Assist is acting up for us. It works on some things but I generally cannot get it to work even with the simplest instructions.I tried troubleshooting it by enabling “Pause on caught exceptions” and “Pause on uncaught exceptions” in devtools; but no exceptions are being raised.

I tried upgrading to the latest version of every Sanity package we use (including AI Assist), but it does not make a difference.

It started happening this morning. Any thoughts on how I can troubleshoot this further for you guys?

Attaching a screenshot where I made a super simple instruction for one field, which doesn’t work (and I tried many different content types9

Just got a report from my editor about this too

Currently looking into it

It seems like sanity is complaining that the AI Document is not a valid document schema.

That's strange because we've been using these schemas for a while now, and AI assist used to work with them just fine.

Same, that schema must be generated dynamically or served remotely

Is it because we added a new schema that broke all the existing ones perhaps? Although a broken schema usually breaks the whole studio

No, we didn't make any changes at all and we have the problem too

It seems like this schema is the culprit: https://github.com/sanity-io/assist/blob/5106347d3e3252d59e3b707522abac8c219f07b1/plugin/src/schemas/assistDocumentSchema.tsx#L374

I am going to open an issue on the assist repository

see https://github.com/sanity-io/assist/issues/16

Nice detective work man! ❤️

Appreciate it, although i still have no clue what's actually causing this, or if the schema validation error is even related. Don't have time to look into where that JSON parsing error is coming from, but i'm assuming it's an API thing.

Yeah we haven’t touched our dependency versions so I’m inclined to agree

⚠️ ⚠️ ⚠️ Sanity AI Assist is broken for at least 2 workspaces, github issue has been filed

We haven't deployed our studio in weeks, so yeah definitely points to an API thing.

Thank you both. We’ve implemented a fix for a breaking change by a third-party API used by AI Assist.