Updating assistant in squads
# support
a
I have noticed that if I update an assistant that is used in a squad by using the "Assistants" section in the dashboard, it does not update the assistant within the squad. Also, when I try to update the assistant within the squad by using the dashboard, I noticed that it sometimes does not update. As a result, I have resorted to updating the squad by using the Patch Squad API call. Is this the right way to go about it at the moment, or is there a better way? It would be nice if updating the assistant in the "Assistants" section updated every instance of that assistant...
v
@Abe Updating an individual assistant within the "Assistants" section of the dashboard does not automatically update instances of that assistant used in squads. This is because each squad maintains its own version of the assistants to ensure stability and prevent unintended consequences from updates. The approach you've taken by using the Patch Squad API call to update the assistant within the squad is correct. This method gives you control over when and how the squad's assistants are updated, allowing you to test and verify changes before applying them to the live environment. While it might seem convenient for updates to propagate automatically, this could lead to issues if the changes have not been thoroughly tested within the context of the squad. Therefore, manual updates using the API ensure that developers can manage updates carefully and maintain the integrity of their squads. If you have any further questions or need assistance with the update process, please feel free to reach out to support for more detailed guidance.
You can continue this conversation by mentioning me in the message.
a
is there any way to update the assistant within the squad by using the dashboard and not having to use the API?
s
@Abe ideally it should update the assistants if you have used the assistant id of the assistants. it might be one of the chances it has failed can you please try again.
s
Marking as complete because of no response.
4 Views