Is it possible to dynamically update the active script node via the Platform API during an ongoing interaction without triggering a full session reset?
We are deploying a Premium App that relies on external data actions to determine script branching logic. When we attempt to POST to /api/v2/interactions/{id}/script with a new nodeId, the Architect engine acknowledges the payload but fails to advance the agent to the new node in the UI, effectively locking the script state. The interaction remains active, but the script progress bar does not update, and subsequent API calls return 400 Bad Request errors citing an invalid state transition. This behavior persists across both PST and EST regions, suggesting it is not a regional configuration issue. We need a reliable method to programmatically steer the script flow based on real-time customer attributes without forcing the agent to restart the interaction.
Make sure you verify the interaction lifecycle state before attempting the POST request. The script engine often rejects node changes if the interaction is not in an active talking state.
{
"nodeId": "new-node-uuid",
"reason": "dynamic_update",
"forceAdvance": true
}
This usually happens because the default API call lacks the forceAdvance flag or the token scope is insufficient for script manipulation. In JMeter load tests, I see this error when the thread group does not wait for the interaction.update webhook event before sending the payload. The Platform API acknowledges the request, but the UI state does not sync immediately.
Check your OAuth scopes. You need interaction:write and flow:write. If you are simulating high concurrency, add a small delay between the data action response and the script update POST. This prevents race conditions where the Architect engine is still processing the previous node transition. The 401 or 409 errors are common if the timing is too aggressive.