Workflow Inbound Calls Ending at 10 Minutes – Need...
# support
d
Hi Vapi team, I’m reaching out because I’m using a workflow-connected phone number, and every inbound call routed through this workflow consistently terminates at exactly 10 minutes. I successfully updated the workflow via API to: { "maxDurationSeconds": 1800 } The workflow update was accepted without errors. However, when calling through the associated phone number, the call still ends at the 10-minute mark. I also attempted to update the phone number itself via: PATCH /phone-number/{id} with: {"maxDurationSeconds": 1800} but the API returned: {"message":["property maxDurationSeconds should not exist"],"error":"Bad Request","statusCode":400} This makes me think the phone-number resource may not yet support changing call duration for workflow inbound calls. My question: Is there currently any supported way to allow inbound workflow calls to last longer than 10 minutes, and if so, what is the correct endpoint or configuration needed to increase the call duration? Happy to provide additional details if needed. Thank you!
c
Hi David Toelle, If you are looking to extend the duration for inbound calls routed through a workflow, note that setting the
maxDurationSeconds
parameter in your workflow should control the call duration. If you are encountering issues with the call ending at 10 minutes despite setting
maxDurationSeconds
to a longer period, it may be worth ensuring that your workflow configuration is correctly applied and checking if there are any specific policies or settings at the phone number level that might be overriding this setting. Currently, modifying the phone number directly to extend
maxDurationSeconds
is unsupported, as indicated by the "Bad Request" response you received. Instead, focus on ensuring the workflow settings are correctly configured, and verify any call handling settings specific to your Vapi server.