Trying to update an existing Web Messaging deployment via the PATCH endpoint /api/v2/conversations/messaging/deployments/{deploymentId}. The payload includes the configuration object with launcher.position set to bottom-right and theme.colors.primary updated to a custom hex code. The API returns a 200 OK, and the response body reflects the changes. However, the embedded widget on the test page still renders in the default top-left position with the old color scheme.
Here’s the relevant JSON patch:
{
"configuration": {
"launcher": {
"position": "bottom-right"
},
"theme": {
"colors": {
"primary": "#FF5733"
}
}
}
}
I’ve verified the deployment ID is correct by hitting the GET endpoint first. The configuration field in the GET response also shows the new values after the PATCH. It feels like the frontend SDK isn’t pulling the latest config or there’s a cache layer I’m missing. No error messages in the browser console. Just the old UI.
Is there a separate API call to invalidate the config cache? Or am I missing a field in the patch that tells the system to push the config update to the edge?