Can a single VAPI workflow handle ~600 branches (1...
# support
j
Hi all—looking for guidance on designing a large decision tree in the VAPI workflow panel. Use case * Based on an early user response, we need to route into one of ~**600 different questionnaires**. * Each questionnaire is ~**10 questions** long. * Goal: keep authoring/maintenance sane and performance stable. What I’ve considered * One mega-workflow with 600 branches (simple but possibly heavy). * A light router workflow that redirects into separate child workflows Questions 1. Hard limits: Is there a practical/official limit on the number of branches/nodes a single workflow can contain (e.g., 600 branches x ~10 questions)? Any known performance or loading issues at this scale? 2. Structure options: * Is it viable to keep all 6000 nodes inside one workflow? Thanks in advance!
c
Hi, currently workflows is under development.
6 Views