It is not clear to me as the documentation of this field is sparse if this is actually a bug or the intended behavior.
The JS and .NET documentation don't claim anything while the Python documentation claims this to be a unique result id. As I imagine that this id is created server-side I would expect the behavior to be the same for all SDKs. And I am sure in the past when we first started using the resultId, it was unique for each result, but now that behavior changed.
From my latest observations with the latest SDK (1.36.0 and 1.38.0) and 1.24.1, this is not the case anymore. The ResultId seems to only change after a speech end detected event. I logged a few of the event on our application side and here it is not clear what the difference between the ResultId and the Id in the json object is, as the Id in the json object changes for every request. When comparing the ResultId with the sdk debug logs it correlates to the X-Request-Id. I would expect a request id also to be unique here.
Here an excerpt of our application logs. The SDK debug logs are also attached with a few repeating/similar lines removed to honor the body limit.
What happened?
It is not clear to me as the documentation of this field is sparse if this is actually a bug or the intended behavior.
The JS and .NET documentation don't claim anything while the Python documentation claims this to be a unique result id. As I imagine that this id is created server-side I would expect the behavior to be the same for all SDKs. And I am sure in the past when we first started using the resultId, it was unique for each result, but now that behavior changed.
From my latest observations with the latest SDK (1.36.0 and 1.38.0) and 1.24.1, this is not the case anymore. The ResultId seems to only change after a speech end detected event. I logged a few of the event on our application side and here it is not clear what the difference between the ResultId and the Id in the json object is, as the Id in the json object changes for every request. When comparing the ResultId with the sdk debug logs it correlates to the
X-Request-Id
. I would expect a request id also to be unique here.Here an excerpt of our application logs. The SDK debug logs are also attached with a few repeating/similar lines removed to honor the body limit.
Version
1.36.0 (Latest)
What browser/platform are you seeing the problem on?
Node
Relevant log output