A tool call the agent decided on before being interrupted still executes afterward, so an action like hanging up can fire even though the caller is still on the line.

What this is

Filed as Tool fire after cancel, the name every report of this mode is collected under.

A failure mode is one named thing that goes wrong on a live call. This record carries every public report of it the atlas has found, in each reporter's own words, and a status that moves only when a re-check stores the artifact behind the move. Status acknowledged: the thread it was reported in has been acknowledged upstream.

Evidence

Every independent public report of this mode, newest first: who wrote it, where, when, what they said, and the link back to the post it came from.

1. A reporton GitHub issues2026-07-19

   Withdrawn: collected in error: a pull request is a change somebody wrote, not an independent report of a call that went wrong.

   How a report comes down

   first seen 2026-07-19 · fetched 2026-07-25T17:50:31Z · body sha256 4891230123214ad1

2. mannyb223on GitHub issues2026-07-10pipecat

   Description A function call requested by a generation that was interrupted/discarded still executes. When that function is terminal — an end_call / hangup tool — the bot hangs up...

   https://github.com/pipecat-ai/pipecat/issues/4997

   first seen 2026-07-10 · fetched 2026-07-25T17:50:31Z · body sha256 4891230123214ad1

Each quote is at most 30 words around the reported failure and links to the post it came from. If you wrote one of these and want it off this page, the removal path takes it down within 24 hours.

What is measurable

Evidence tier: Atlas record: every field on this page traces to a fetched public artifact.

What 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.
• 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.

# the timing incidents in one recording, ranked
hotato autopsy ./call.wav

The tier above is what this record establishes on its own: linked sources, an artifact behind every status move, and timestamps that trace to a fetched response. To put a number on your own call, hotato autopsy reads a recording you already have and ranks the timing incidents in it. hotato is MIT and runs locally. getting started.

Status history

A daily re-check reads every source thread on this page. The status moves when that re-check stores the link, the quote and the date behind the move, so every state on this record is one you can open.

1. open→acknowledged2026-07-26

   issue closed (not_planned)

   https://github.com/pipecat-ai/pipecat/issues/4997

   evidence dated 2026-07-23

Related modes

Entries this one shares evidence with. Each line names the share that put it there: a stack both were reported on, a post that named both, or the detector kind that measures both.

• TTS word drop context racefixedVFA-2026-0015

  A queue-ordering race in assembling the agent's own spoken output into conversation history drops the turn's final word from the stored...

  shares: reported on pipecat; reported on github

• Dead-air after calleropenVFA-2026-0006

  The caller finishes and the line goes silent for seconds before the agent responds, with no audible acknowledgement in between.

  shares: reported on pipecat; reported on github

• Endpoint misdetectionacknowledgedVFA-2026-0002

  End-of-turn detection fires at the wrong moment, so the agent either answers before the caller has finished or waits after they have.

  shares: reported on pipecat; reported on github

• Silent TTS failover deadlockacknowledgedVFA-2026-0009

  The agent's speech synthesis silently produces no audio even though it logs the turn as spoken, and the safeguard meant to detect and...

  shares: reported on pipecat; reported on github

The record

Atlas id

VFA-2026-0008

Mode id

pat_84c2e63007c368f3aeecc01a

Content digest

sha256:84c2e63007c368f3aeecc01aca88fe615f33df03e8894ba645d646e9de86bf11

First reported

2026-07-10

Last reported

2026-07-10

First seen by the atlas

2026-07-19T01:36:37Z

Last re-checked

2026-07-19T01:36:37Z

Reported on

pipecat

Sources

GitHub issues

Scope

1 independent public report across 1 source. This entry states where the mode has been reported; where else it can occur is what the next report settles.

References

Every link this entry stands on: the post behind each report, and the artifact behind each status move.

1. reporthttps://github.com/pipecat-ai/pipecat/issues/4997 · mannyb223 · GitHub issues · 2026-07-10

Machine surfaces

Removal

If you wrote something quoted on this page and want it gone, one email 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.