API Streaming Call responses not saved

I am saving openAI API responses to my database as done here in the last step. It worked well until suddenly today it stopped working. In my OpenAI logs I can see that everything is working. I get my desired output but that output is not saved anymore as it previously did as shown here in step 5. I changed nothing - it just stopped working overnight. Anyone else having this issue?

I get this message in my logs: Workflow error - Sorry, we ran into a temporary bug and can’t complete your request. We’ll fix it as soon as we can; please try again in a bit!

Yes having the same issue now when working with the full text from a text stream. Using openrouter as well. Just started today for some unknown reason.

I reported this as a bug to bubble yesterday. I found a workaround, which is not to use the “text stream’s full text”. Instead (and depending on whether the api has this data), use the final output that’s provided at the end. So for the “responses” api, that event is called “output_text.done”, and you want “data.text”. Which contains the full text. When I map that that out I’m not getting errors.

This workaround only works if the api stream actually provides a full output at the end.

Here’s an image of my setup that implements this workaround.

1 Like

Yeah, same for me…

We’re seeing the same issue. Initially openAPI streaming response completion was not being detected. Today, the end of the stream is detected and text so far is displayed, however, on completion, the full text isn’t saved to the database.

This was all working fine a couple days ago.

a few of us are also having this issue. still unresolved.

I’m in the same boat. wasted the last 4 hours trying to work around this. :frowning:

It started saving again (I received the workflow failed please try again later message before) but with empty values. @emmanuel @josh Please forward this bug to your devs to fix it.

This looks like a temporary Bubble workflow bug affecting streaming API calls. If your OpenAI responses appear in the logs but aren’t saved, it’s likely the workflow didn’t fully complete. A quick workaround is to add a small delay before saving the response or use a backend workflow to handle the database write. Otherwise, it should resolve once Bubble fixes the underlying issue.

Seems to be working correctly now on our end. No reply to my bug report though…

1 Like

Thank you, this fixed my issue which appeared also.

1 Like

this is solved now for me too. looks like the bubble devs fixed it. still not sure why it even started.

1 Like