Erkam
04/15/2026, 5:29 PMAI Evy
04/15/2026, 5:29 PMAI Evy
04/15/2026, 5:29 PMno_interruption_allowed field should control whether the agent can be interrupted during speech [(1) ]() . When set to false, the agent should be interruptible .
However, there is a related community discussion about interruption issues with Custom LLM implementations [(2) ]() . In that case, users experienced inconsistent behavior where certain flags didn't work as expected .
For your specific interruption issue, here are some troubleshooting steps based on the documentation:
In Response Events:
When sending response events, ensure no_interruption_allowed is set correctly [(1) ]() :
- no_interruption_allowed: false should allow interruptions
- no_interruption_allowed: true prevents interruptions
For Agent Interrupt Events:
If you need to force an interruption, you can use the agent interrupt event with no_interruption_allowed: true recommended to prevent the agent from being interrupted again during that forced speech .
Handling User Interruptions:
According to community guidance, if a user interrupts while you're generating a response, you can drop the current response and generate a new one [(3) ]() . If you're in the middle of a tool call, you may want to complete it and provide an intermediate wait message .
If the interruption behavior is still not working as expected with no_interruption_allowed: false, this may indicate a technical issue that would require direct support investigation.AI Evy
04/15/2026, 5:29 PMAI Evy
04/15/2026, 5:29 PM