Hi Romek
The issue you are encountering with the GetAnswers
method when using the overload with a QnaId
instead of TextMessage
appears to be related to how the QnaId
parameter is being processed. Since the method works fine when using TextMessage
, the problem likely stems from either an update in the API behavior or a misconfiguration in handling the QnaId
. To troubleshoot this, you should first check the official documentation or release notes for any recent changes that might have affected this functionality. Additionally, reviewing the code implementation of the GetAnswers
method can help ensure that the QnaId
parameter is correctly formatted and passed. It is also important to verify if there are any specific requirements or restrictions when using QnaId
, as these could be causing the 404 Bad Request error.
For further insights, you can refer to the Microsoft Q&A discussion and a related Stack Overflow thread that address similar issues with the GetAnswers
method.
If you need any further assistance, please let me know!
Thanks