conscious-sapphire•3mo ago
/interact API returns 500 on new projects + doesn't update after publish
I'm getting a 500 Internal Server Error from the /interact API when using newly created projects, even after publishing them.
The exact same request works fine on older projects, but fails on new ones created today.
Also, on older projects, even after publishing a new version, the /interact API still responds using the previous version of the flow. It's like the new publish doesn't take effect.
This started happening yesterday (old version sticking), and the internal error started 2–3 hours ago.
Can someone from the team look into this? It seems like the API isn't syncing properly with the latest project state.
https://docs.voiceflow.com/reference/stateinteract-1


4 Replies
Hi! Here are the two separate issues you’re seeing and the usual causes/fixes.
1. 500 “Internal Error” on brand-new projects
• A new project must be compiled once before the runtime has anything to execute.
– For the development alias click Run on the canvas.
– For the production alias click Publish.
If neither of those buttons has been pressed yet the DM runtime can’t locate a version and the first /state/.../interact call will return a 500. 2. New publish isn’t reflected when you call /interact on an older project • Make sure the request’s versionID header is an alias ("development" or "production") and not a hard versionID string. A hard ID always resolves to the exact build that existed when you copied it, so later publishes will never appear. • If you omit the header the runtime defaults to the production alias, so a fresh Publish should be immediately picked up on the next request. Curl example that always gets the newest production build: If you’ve already pressed Run/Publish and are calling an alias yet still seeing the 500, try creating a blank test project, hitting Run once, and then calling the endpoint; if that still returns 500 that indicates a transient backend issue and you can retry in a few minutes. Docs for reference: https://docs.voiceflow.com/reference/updating-your-version Hope that helps clear things up! 🎉
– For the development alias click Run on the canvas.
– For the production alias click Publish.
If neither of those buttons has been pressed yet the DM runtime can’t locate a version and the first /state/.../interact call will return a 500. 2. New publish isn’t reflected when you call /interact on an older project • Make sure the request’s versionID header is an alias ("development" or "production") and not a hard versionID string. A hard ID always resolves to the exact build that existed when you copied it, so later publishes will never appear. • If you omit the header the runtime defaults to the production alias, so a fresh Publish should be immediately picked up on the next request. Curl example that always gets the newest production build: If you’ve already pressed Run/Publish and are calling an alias yet still seeing the 500, try creating a blank test project, hitting Run once, and then calling the endpoint; if that still returns 500 that indicates a transient backend issue and you can retry in a few minutes. Docs for reference: https://docs.voiceflow.com/reference/updating-your-version Hope that helps clear things up! 🎉
conscious-sapphireOP•3mo ago
Wow! That was actually helpful😆 Fixed it
Used an versionID string instead of "development" or "production". Then dublicated the projects out of frustration without clicking it on run first 🤣 Learned something new lol
sensitive-blue•3mo ago
😄 @Abdullah Also had that already that the chatbot here helped me out 😄
conscious-sapphireOP•3mo ago
Hahaha XD