@buildingsomething - hm, no the plugin isn’t down. Seems to be working on my end. Not sure why you would have hit that error. For the sake of debugging:
- Are you still using the “Ensure Connected” action?
- How long were you getting that error?
- Did the error go away on page reload?
If you have any other details, please let me know, so I can troubleshoot more effectively.
As for a backup, you can definitely set it up to run the “Fallback” workflow, which doesn’t stream. You can set up either an action or a workflow to run conditionally on “Connected?”. So if Connected? is yes, run “Send Message w/ Server” as usual, and if “Connected?” is no, run the fallback action. That’s the intent of those states and actions.
As mentioned above, this is a temporary stop-gap until v6 is ready, which should be a big improvement in availability.
Receiving the error again unfortunately. I also briefly had message come up from Bubble about my custom domain having an issue but that was just for a second and so not sure if it’s related?
I’ve tried it both ways:
- With the server using the ‘Ensure connnected’ = that error message
- With the server without ‘Ensure connected’ = nothing happens, no error and no text returned from
WIth the fallback, not sure I understand where you set the conditional statement? I can’t choose the ‘Ensure connected’ as an Only When statement and when I use it as an action it throws up that error and stops the workflow so can’t put the fallback option to come after it.
Also, I’m using the ‘When message generation complete’ event we set up yesterday to write the generated text as a record to the database but this doesn’t work with the fallback. And when I create the message record directly from the fallback action, it only gives me two options the error message or the Response message (which includes the full json object message).
Hi there, I did not see an option to set a system message; where should I add that field?
Okay, sorry, my explanation wasn’t super clear.
The “Connected?” state is what you put in the conditional expression. You would write an expression like:
- If “Connected?” is yes:
** then in workflow, use action → “Send Message w/ Server”
- If “Connected?” is no:
** then in workflow, use action → “Send Message non-streaming (fallback)”
The expression could be on a full workflow, or on actions within the workflow. Either should work.
Also note that the container should be connected by default, so you don’t necessarily need to run “Ensure Connected” before using the conditional “Connected?”. It should be “yes” when you load the page. The Ensure Connected action just tries to re-establish it if it has disconnected.
The “Ensure Connected” action runs before the “Send Message” action. So you don’t use the response from that action. You could run the action, then have the two send actions after it, with the conditional statements on them.
Does that make more sense?
I can update the demo app with this setup later this evening when I’m back at my computer.
@enbitious - You can set one of the messages to be a role of “system”. Then set the content to the trainer content. Make sense?
@enbitious - exactly. Give that a spin and see if it works.
This is a brilliant plug-in that solves a crucial need. Thanks for building it!
My issue is currently with the system message and conversation history. I’ve got a pretty long system message that gets the AI to be a tutor with a set sequence of instructions.
Unfortunately, right now, the AI can’t follow through on my instructions because I think it loses some of my system message. It ends up behaving incorrectly.
I’m happy to try the temporary hack to get around this until a more proper fix comes for it. Regarding the above solution you provided, would you mind explaining it further? I’m not quite sure how to do it (still learning Bubble!).
@mdajinani - your understanding is correct, the system message won’t be included after 8 messages are in the history.
For the workaround, you’d write a conditonal check “If Message History :count > 8”, then set your system message again.
I’ll add an action tonight to set a static system message, which will simplify this, as it’s pretty common to want a system message that is consistent across the conversation.
This would be amazing. Thanks!
Ah ok, I just realised what you meant. ChatGPT-DataContainer has a field called Connected?, and so the expressions is:
Only when ChatGPT-DataContainer A’s Connected? is "yes"
In which case, I shouldn’t need the Ensure connected action as it will just use the fallback if it’s not working? Unless there’s another reason to use it?
Also, any update on that issue we encountered with the message history not loading for the pre-loaded chat questions and answers? I’ve found that even with that pause we added, it still sometimes doesn’t load.
Is there an error with server?
Seems to be resolved 
forced me to at least implement the workaround I had been postponing.
@sacoetzee - thanks for mentioning this. I just saw it as well. Should be fixed for the moment, with a more permanent fix incoming.
Same thing here, and now some messages fail to respond
@georgecollier - Okay I’m on it. Will report back soon.
Is sending messages without using your server now more reliable than sending with the server? What’s the best option to use?
@georgecollier - I’m not sure yet. The fallback option should work even if streaming isn’t. And the “Send Direct to OpenAI” should work even if the servers are completely offline (only problem there is client can see API key; if they provide their own, this isn’t an issue).
I haven’t reproduced the issue you’re seeing though yet, so I’ll have to check in again in a few minutes. Stand by 
