Assistant status "completed" throughout the conversation

(Samuel) #1

Hi all!

I have been testing an assistant and I noticed in the debug and in the run history that sometimes it defaults to “completed” every time it responds. Other times it shows “awaiting_response” like it is supposed to.

The “completed” status is an issue because it slows down the response rate and triggers a flow too early.

I have rephrased the instructions and the goal for the assistant a few times but notice it keeps happening. Any tips on why this might be happening?

The image below shows two chats that are active at the time. (The users are on zoom with me so I can see their screen). One is complete (even though it is still running, albeit slowly).

Thanks all!

(Nathan Stults) #2

Unfortunately the AI controls whether or not the conversation is complete. Other than how you write the “goal” section, you can also include additional rules in the “instructions” about when to complete a conversation. The AI won’t always listen though, especially 4o mini.

Another technique you can use is to have some required output fields that will strongly indicate that a conversation is completed once they are filled. We do a final check, before completing a conversation, to see if all required output fields are filled in, and if any are not, we ask the AI to double check to make sure it really wants to end the conversation. So that’s a trick you can use as well.