Hi Vapi Support, I'm experiencing an issue where my assistant configuration gets reverted after I update it via API. Setup: I have two assistants (production and development environments) Both use the same update script but different assistant IDs Updates are applied programmatically via the Node.js SDK Problem: When I run my update script, the assistant configuration updates successfully initially, but after some time it reverts to the previous configuration. Update flow: 1. Get assistant ID by name 2. Update tools via assistants.update() 3. Get tool IDs 4. Update assistant with new configuration + toolIds Questions: Is there a known issue with configuration persistence? Could there be another process or dashboard action overwriting my changes? Are there any rate limits or validation issues that might cause silent rollbacks? Should I use a different API method to ensure changes persist? The update completes without errors, but the configuration doesn't stay. Any guidance would be appreciated. Thanks!

Hey, this usually happens when another script, webhook, or dashboard change is overwriting your updates after they go through. If tools and config are updated in separate calls, a race condition can also cause the older version to “win” later. I’d recommend logging all update requests with timestamps and checking if anything else is touching those assistant IDs. Also try updating tools and config in one flow instead of multiple steps, and avoid reusing cached configs. Do you have any background jobs, CI pipelines, or manual edits that might be redeploying these assistants? @kiryhanchik

Hey! No background jobs or CI pipelines. The only two things that touch the assistant config are: 1. My update script (run manually) 2. The assistant-request webhook, which returns a full assistant config on every incoming call But in this case the revert happened without any incoming calls, so neither of those triggered. Not sure what caused it.

Hey, thanks for explaining, that webhook returning the full assistant config is very likely what’s causing this. Even if no calls happened recently, Vapi can replay or reuse that response, and if it contains an older version, it can quietly overwrite your latest updates. I’d suggest we review what your webhook is returning and make sure it’s always pulling the latest config and not something cached. We can also align it with your update script so there’s only one real source of truth and no conflicts.. Let’s discuss this more privately I’m confident we can lock this down so your changes stop getting reverted. @kiryhanchik

i think i found the problem, thank you brother, really preciate it. new day - new brain