We have a large survey (~40pages ~400 questions) with lots of logic. We use API to pull the response data, and do all the analysis internally in as close to real time as the API allows. The branching means that it’s never too long for an individual to take, but I’m wondering if we will hit any issues as the survey object size continues to grow. At the current rate we expect the survey may grow to ~100 pages with ~1500 questions by year’s end. Anything we should be aware of?
We have never gotten close to building a survey as large as you are describing, But we have built some complex surveys and found that as we added skip patterns and logic tests, the time lag between each page began to increase.
There is not a hard limit as there are so many factors to consider (complexity of the survey, what features are being utilized, etc.), but you might see some slower performance in the application with a survey of the size that you have mentioned.
I might suggest reaching out to SG Support for best practices:
I hope this helps!