@joaquintorroba ahh, okay. In that case, you can set your api key in the Send Message Direct to OpenAI workflow, instead of the plug-in tab. That should do it.
Note though, that you probably only want to use that action if your users provide their own keys (ie, your not providing your key for everyone). Otherwise your key could be found by an unsavoury type.
If your are providing the key, definitely use Send Message w/ Server
Perfect, thanks @launchable .
One last quick question: How can I ensure that as the chatbot replies, there’s an auto-scroll to the latest response so users don’t have to manually scroll down? I’ve tried using ‘Scroll to’ without success – maybe I’m doing something wrong?
The way I’ve done it is to add an empty dummy element to the repeating group that’s showing the Display Messages. Then you scroll to that every .5 seconds or so, while the “Curently Streaming?” is true.
This is detailed more up above. It works quite well imho, but let me know if you have less luck with it.
Any updates on function calling? Still getting no response from OpenAI after a successful API call. is there maybe a timeout if the API takes too long to reply?
Thank you for your continued dedication to building and maintaining this solution. Keep up the excellent work, and thank you for your proactive approach.
Hey @hugors00 - I don’t think so, but I’ll look into this. Thanks for letting me know.
Edit - I’m not seeing any issues with this model
Are you requests with other models all working fine?
One thing you could try is adding an error-capture event to the page, to see if an error is coming back. The only thing I can think of atm is that you might be getting a “model unavailable” error, if you don’t have access to 16k, but I think this is probably not the case, as I think 16k is available to every one.
What would be the best way to let the user know about an error? An example is occasionally when an input is typed in and “generate” is clicked, no text will show up. If that’s going to be the case is there a workflow/element that can be added?
I saw one talking about fallback messages but I’m not sure how that should be used… or how to check if the message is gonna fail.
@gulbranson.nils - currently errors all throw different events - e.g., if an API key is invalid, there’s an API Key error event. If there is a timeout with the API, there’s a timeout error event, etc.
So with the current version, you could set up events to capture each of these errors, and show them in an alert or a text element, etc.
In the next release (v6), this will be simplified, and there will be a single error event, and there will just be a different message set inside the Data Container. Then you can set up a single event to handle errors, and show the messages based on the message in the Data Container. Hopefully this will make it simpler to handle any issues that pop up (and hopefully with the rebuild there will be no errors to handle in the first place )