Conversation Locked even when there is no other process actually working on that conversation, while using Azure Logic Apps

API Bugs
, , ,
1

Hello Everyone,To give you a bit of context, I have an azure logic apps that basically interact with OPENAI API through API calls; after I create an HTTP request with responses endpoint and having the conv_id attached to the request, some times for no real reason the API give me the following error

{ "error": { "message": "Another process is currently operating on this conversation. Please retry in a few seconds.", "type": "invalid_request_error", "param": "conversation", "code": "conversation_locked" } }

However, I am sure that no other process is currently operating on this conversation, because I have made sure that the parallelism is disabled, so the execution of the azure logic app is strictly in a queu and no other logic app are using the same conv_id.

I was wondering if this is a bug, and if there is a way to check on the state of a conversation in real-time before sending a request or anything. please advise

2

Hello, so I figured out the reason behind the issue. I don’t know if it is a bug from OpenAI side or a limitation from Azure Logic Apps side or both.

The reason is that when the HTTP action on Azure Logic Apps is using the asynchronous pattern, when then retry to access the API with the location URL , the conversation is shown as locked due to the fact that the responses API is still generating the response ; However when you put it to Synchronous request, there is a time limit of 2 minutes, if the request takes more time than 2 minutes then the Azure logic Apps will forcefully close it for you.

I have been trying to see what could be a solution for such a task, I might attempt webhooks; However I am not using a programming language and I don’t know if it is feasible in azure logic apps

1 Like