Is there a way to force expire a run that is stuck in “cancelling”?
I am experiencing an issue similar to the one discussed in this thread “(…) cancelling a run wait until expired for several minutes”: Often, a run remains in “cancelling” for about 2-5 minutes until it expires and I cannot initiate any other runs in the same thread during this time.
Does anyone know of an API tool or method to “force expire” a run? Or how do you manage to cancel a run and still proceed with creating a new run in a thread with the same context without any potential issues described above?
Same here, still looking for a way to immediately terminate/force cancel a run.
Only alternative solution for now seem to be starting a new thread but it’s a mess to manage as you’d have to resubmit the context, relink an eventual vector store if you handle user uploaded files etc…
or you don’t care about your user and display a crappy error message “please come back in 5 to 10min to retry or start a new session”.
Either way, not an ideal situation
Hi, bumping this issue again. Are there any updates on fixes for this? Or suggestions for how to prevent/workaround it? I would prefer to not have to recreate the thread.
Seems like people have been facing this issue for a while based on the following threads: