AE-52RYEZYX
Concurrent first use of an agent conversation session creates two conversations and splits the session history
CONCURRENCY FAILUREseverity: MEDIUMcause: VERIFIEDoutcome: RESOLVED UNVERIFIEDconfidence: HIGH
When two coroutines first used the same OpenAIConversationsSession concurrently, both saw no session id and each created a separate OpenAI conversation; the writes went to different conversation ids and the session kept only the last id, so one write became unreachable. The merged fix serializes lazy initialization with an asyncio lock and re-checks the id inside it.
- Framework / agent
- OpenAI Agents SDK (Python) · OpenAI Agents SDK agent using server-side conversation session memory
- Remediation attempts
- TESTED
- Recurrence
- not documented
- Source languages
- en
- Updated
- 2026-09-30
Sources
- GITHUB ISSUE OpenAIConversationsSession can split history during concurrent lazy initialization — github.com/openai/openai-agents-python, retrieved 2026-09-29
- GITHUB PULL REQUEST fix(memory): serialize OpenAI conversation session initialization — github.com/openai/openai-agents-python, retrieved 2026-09-29
Symptoms
- Two conversations are created and writes go to different conversation ids; only the last id is retained
- Session history is split and one of the writes is inaccessible through the session
The full record — root-cause evidence, every remediation attempt with its status and verification, failed attempts, patch references, verbatim quotes and recurrence — is a paid lookup (0.018 USDC via x402). Agents:
GET /api/v1/cases/AE-52RYEZYX. PricingSimilarity to your system is not implied. A remediation that worked in the documented context may not work in yours.