Tool call cancel race stuck in progress

acknowledged

2 independent reportsacross 1 sourceon 1 stacklast reported 2026-08-09

What this is

When the caller interrupts a tool call before the system has finished marking it as started, the call gets permanently stuck flagged as in-progress, stalling the conversation.

Status acknowledged: the thread it was reported in was acknowledged upstream.

Evidence

scttbnsn2026-08-09pipecatGitHub issuesgithub.com/…/5263

...and calls the real reset(), so nothing about the drop is simulated. python """Repro: interrupting a Flows tts_say/function action leaves the ongoing-actions count stuck.""" import asyncio from unittest.mock import AsyncMock,...

First seen 2026-08-09 · our copy fetched 2026-08-09T21:07:06Z · SHA-256 of that copy begins 741fb84adf146351… · profile

OlliTapio2026-02-06pipecatGitHub issuesgithub.com/…/3661

...version 3.12.12 ### Operating System MacOS 26.2 ### Issue description When we manage to interrupt the function call before the FunctionCallInProgressFrame has been sent, the function call gets stuck IN_PROGRESS...

First seen 2026-02-06 · our copy fetched 2026-08-01T18:10:29Z · SHA-256 of that copy begins 8eb817a4d4602a29… · profile

Quotes run to 30 words around the reported failure and link to the post.Add your call to this entry Take a quote down within 24 hours.

What is measurable

Signal	This record stands on its own linked sources. To put a number on your own call, `hotato autopsy ./call.wav` reads a recording you already have and ranks the timing incidents in it.
Establishes	Every report below links to the original post and names the handle that wrote it; the quote is at most 30 words around the reported failure. What else it establishes, and what your own trace settles The status changes only when a re-check stores the evidence link, the quote and the date behind the change. Every timestamp comes from the fetched artifact it describes, recorded with the sha256 of the response body it was read from. What your trace settles Reproducing the mode on your own stack is the next step: the reports below carry the configuration each reporter was running.
Tier	Atlas record: every field on this page traces to a fetched public artifact. hotato is MIT and runs locally, getting started.

Status history

Date	State	What moved it
2026-08-17	openacknowledged	issue closed (not_planned) evidence dated 2026-04-08

Mode	Status	Shares
TTS word drop context race	fixed	reported on pipecat; reported on github
Orphaned interrupted tail flushed post goodbye	open	reported on pipecat; reported on github
Voicemail detected end call frame dropped	open	reported on pipecat; reported on github

Discussion

Reader discussion of this mode: what fixed it and what did not. The reports above are attributed and linked; a comment is a comment.

Open this discussion on GitHub

The record

Ids, digests, every link this entry stands on, and how to take a quote down

Atlas id	`VFA-2026-0024`
Mode id	`pat_3eb23e05b185cec32e61cf0e`
Content digest	`sha256:3eb23e05b185cec32e61cf0eb7a6d652c205fad8f8a4721ed1b4e0e6ce7f4551`
First reported	`2026-02-06`
Last reported	`2026-08-09`
First seen by the atlas	`2026-02-06T08:50:52Z`
Last re-checked	`2026-08-09T20:54:20Z`
Reported on	pipecat
Sources	GitHub issues
Scope	2 independent public reports across 1 source. This entry states where the mode has been reported; where else it can occur is what the next report settles.
References	reporthttps://github.com/pipecat-ai/pipecat/issues/5263 · scttbnsn · GitHub issues · 2026-08-09 reporthttps://github.com/pipecat-ai/pipecat/issues/3661 · OlliTapio · GitHub issues · 2026-02-06
Machine surfaces	feed.json feed.atom feed.schema.json atlas.llms.txt
Removal	If you wrote something quoted on this page and want it gone, one email to atlas-remove@hotato.dev does it. The removal path takes the quote, the handle and the link off this page, out of the feeds and out of the llms.txt within 24 hours, and tombstones the id so the entry cannot quietly return at a new address.