---
type: email
from: Lucas Wang <notifications@github.com>
subject: Re: [openai/openai-agents-python] Response cancellation broken due to

 tuple assignment bug in Realtime API (Issue #1951)
received: 2026-03-06 08:10:41
date_header: Mon, 20 Oct 2025 21:53:21 -0700
priority: high
status: awaiting_approval
uid: 33192
---

## Email Content

**From:** Lucas Wang <notifications@github.com>
**Subject:** Re: [openai/openai-agents-python] Response cancellation broken due to

 tuple assignment bug in Realtime API (Issue #1951)
**Date:** Mon, 20 Oct 2025 21:53:21 -0700

### Body (preview)

gn00295120 left a comment (openai/openai-agents-python#1951)



## Potentially Related Issues



This bug may be the root cause of the following reported issues:



### Highly likely related:

- #1907 - Guardrail interruption fails with "Conversation already has an active response in progress" error

  - User specifically notes: "_response.cancel is triggered if turn_detection.interrupt_response is **not set**_"

  - This aligns perfectly with our bug: when `interrupt_response=False`, the tuple bug prevents `_cancel_response()` from being called

  - Timeline: Issue reported 2025-10-16 (34 days after bug introduced in PR #1646)



### Possibly related:

- #1912 - Output guardrails don't work correctly (Python vs Node.js behavior difference)

  - Manual `session.interrupt()` doesn't work as expected

  - May be partially caused by broken response cancellation logic



Both issues appeared after PR #1646 (2025-09-12) which introduced this bug.



-- 

Reply to this email directly or view it on GitHub:

https://github.com/openai/openai-agents-python/issues/1951#issuecomment-3424663632

You are receiving this because you are subscribed to this thread.



Message ID: <openai/openai-agents-python/issues/1951/3424663632@github.com>

---

## Suggested Actions
- [ ] Reply
- [ ] Archive
- [ ] Escalate
