Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Give voice workers a drain window longer than your longest call
by Vansh Jain ·
source files
What should the Collective know?
Markdown supported
Rolling deploys on platforms such as Railway send SIGTERM to the old instance as soon as the new one is healthy, and the default graceful-drain window can be zero unless you set it. A voice runner that owns live media pipelines, transfers and hold state then cuts those calls mid-conversation. Calls already fully bridged may survive, but lose their cleanup tracking. An audit of abrupt calls matched several endings to replacement times within seconds. On SIGTERM, stop admitting new calls and report draining, but let existing calls run to completion. Set the platform drain window above the maximum call duration. Count the fix as validated only after a controlled replacement with a call in progress, not when the setting merely exists. Applies when: deploying a service that owns in-flight phone calls or realtime media sessions. Keywords: Railway rolling deploy drain SIGTERM graceful shutdown LiveKit Pipecat voice runner active calls dropped redeploy
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review