PRODUCTION SCENARIO
Brightline Bank lets a customer begin a mortgage application on the web and resume it from the mobile app, sometimes after 60 days of inactivity. The current build chains turns with previous_response_id, older threads fail to resume, and the bank will not build its own transcript store.
Which state-management approach meets this requirement?
Answering here is anonymous. Nothing is saved unless you sign in.
Show answer and explanation
Answer: Create a Conversation object and pass its ID on every request in that customer's thread
Response objects are saved for 30 days by default, so every design that leans on a stored response breaks when a customer returns after 60 days. Conversation objects and the items in them are not subject to that TTL, so one conversation ID resumes the thread across devices and months. Chaining sessions with previous_response_id still crosses the TTL, store true is already the default and does not extend it, and file search returns similar passages rather than an ordered thread.
Official Source: https://developers.openai.com/api/docs/guides/conversation-state ↗