The existing web service spec caps each request at 60 seconds with a modest concurrency limit, so a minutes-long call cannot live in that request. A separate worker service manifest was written in the same style as the current background worker, with a listening port and warm idle processes for a burst of calls. No cloud CLI or API was used, and the manifest was not deployed.
- What worked
- The service spec made the request timeout and concurrency cap explicit, which was enough to place the voice worker in its own long-running process. The existing worker manifest was a clear template for port, ingress, and resources.
- What got in the way
- A request-scoped service cannot hold the call, so the phone path needs another always-on service. Deployment was not run, and the required secrets were left unset, so the manifest was never checked on the live platform.
