cache issues on API request
i am using the developer versionID and i keep receiving cached result even if i changed the workflow action the server keep responding with old and not existing steps. Are you crazy caching developer server requests? Is going to make developers mad , you should not cache dev calls
2 Replies
Hey there! I know this can feel like the runtime is “caching”, but what you’re seeing is actually the DM API’s session state, not HTTP caching:
• Each request is tied to the userID you pass in the URL.
– The server keeps that user’s stack, variables, and the node it last stopped on.
– If you hit the same endpoint with the same userID, the runtime will resume from that point, even if you’ve changed the diagram in Creator. • How to see your latest changes on the development version
1. After every edit, hit the blue Run button (or press R) on the canvas. This recompiles the development build that the API serves.
2. Start a fresh session:
– Use a brand-new userID or
– Call the “Delete state” endpoint:
This wipes the stored stack/variables so the next POST /interact will start from the first block of your newly-compiled flow. • There is no extra HTTP caching on our side for development calls—the behavior is purely state-based. Give that a try and you should see the updated steps right away. If anything still feels off, double-check that: – You really pressed Run after your last change.
– The request header
– You’re calling with a fresh userID or after deleting the state. Docs for reference: https://docs.voiceflow.com (see “Delete state” & “Updating your development version”). Hope that clears things up!
– The server keeps that user’s stack, variables, and the node it last stopped on.
– If you hit the same endpoint with the same userID, the runtime will resume from that point, even if you’ve changed the diagram in Creator. • How to see your latest changes on the development version
1. After every edit, hit the blue Run button (or press R) on the canvas. This recompiles the development build that the API serves.
2. Start a fresh session:
– Use a brand-new userID or
– Call the “Delete state” endpoint:
This wipes the stored stack/variables so the next POST /interact will start from the first block of your newly-compiled flow. • There is no extra HTTP caching on our side for development calls—the behavior is purely state-based. Give that a try and you should see the updated steps right away. If anything still feels off, double-check that: – You really pressed Run after your last change.
– The request header
versionID is development (or omit it, which also defaults to development).– You’re calling with a fresh userID or after deleting the state. Docs for reference: https://docs.voiceflow.com (see “Delete state” & “Updating your development version”). Hope that clears things up!
i am always deleting the state but not clicking on run as i have intent so i am running from the event and same from api i am starting from the intent and many many times edits i make are not considered