@Sahil I'm sorry to hear you're experiencing issues with your new Assistant integration. It sounds like there might be a discrepancy between the AssistantId you're using in your API call and the one that's registered in the system. Here's what we can do to troubleshoot this: 1. Double-check the AssistantId: Ensure that the AssistantId you're using in your API call matches exactly with the one provided when you set up your new Assistant. This includes checking for any typos or extra spaces. 2. Verify API credentials: Make sure that the API credentials you're using have the necessary permissions to access the new Assistant. 3. Review the API call: Look over the code where you're making the API call to confirm that the AssistantId is being included correctly in the request body or as a parameter. 4. Test with a known working AssistantId: Try using the AssistantId from one of your other Assistants that you know works to see if the issue is with the API call itself or specifically with the new AssistantId. If after these steps you're still encountering the same issue, it might be best to reach out to the support team with details of your AssistantId and the exact error message you're receiving. They'll be able to provide more specific assistance and help ensure your app can go live as planned. Would you like me to guide you through any of these steps in more detail?

in the UI

just not surfacing in the API request

like I swapped out the assistant key in my code with the assistant that works