From time to time the tools calls have the error code 401 unauthorized during the calls even if we do no make any change on the tool. It looks like it happens when we had the existing tool to a new assistant. Do you have registered a similar issue in your backlog? What do we have to do to avoid this problem ?

@Yoann C. I'm sorry to hear that you're experiencing intermittent 401 unauthorized errors. This issue can occur if there's a problem with the authentication process when a tool is called by a new assistant. Here are a few steps you can take to avoid this problem: 1. **Check Credentials**: Ensure that the credentials used by the new assistant are correct and have the necessary permissions to access the tool. 2. **Token Expiration**: If you're using tokens for authentication, make sure they haven't expired. Tokens often need to be refreshed periodically. 3. **Assistant Configuration**: Verify that the new assistant is configured correctly and is using the correct tool endpoint. 4. **Access Control**: If there are IP whitelisting or other access control measures in place, ensure that the new assistant's environment is allowed to make calls to the tool. 5. **Consistent Configuration**: When adding an existing tool to a new assistant, ensure that the configuration is consistent with the other assistants that are able to use the tool without errors. 6. **Logs and Monitoring**: Review the logs for both the tool and the assistant to see if there are any additional clues as to why the authorization is failing. 7. **Support Team**: If the issue persists, it may be beneficial to contact the support team with details of the problem, including any relevant logs or error messages. If you've already checked these common issues and the problem still occurs, it might be a more complex issue that requires further investigation. Please ask support for more info on this, and they can help you troubleshoot the problem in more detail.

@Yoann C. Please ask support for more info on this.

@Yoann C. can you share the call id?