Hi Patrick,
I’m testing the Groq integration using Wappler’s built-in AI panel.
The first prompt works fine, but when I try to send a second message in the same session, I get the following error:
It looks like Wappler is passing a "context" property instead of "content" in the second message, which is not supported by Groq’s API.
Seems that Groq is very strict with which properties are on the message object. The content property is always on it, but we have some extra properties like context that holds information about extra context that needs to be send like the editor content or user selection. Almost all providers ignore unsupported properties, and we do clean them up before sending but seems there was a case that the context wasn't removed. It is fixed in the next update.