Closed ShantanuNair closed 1 year ago
Hi @ShantanuNair. Thanks for reaching out. This feature is still in Beta which is why it isn't documented well. It is still going through some checks before we release it generally. It is available as a production feature but it currently needs to be passed in as detect_entities: "latest"
. Before we release it out of beta, they way it gets passed in might change back to how you have it above. We'll have it documented though when we do release it.
Because it is still in beta, there will likely still be some bugs/regressions/bad performance occassionally. We are working to get it polished and released soon.
@briancbarrow Hi Brian, thanks for the update. I'd like to mention thought that the issue was that the job would fail completely if the option was passed it. We had to avoid passing in the option, else all our jobs were failing.
@ShantanuNair correct. Since our API cannot process it when it is passed in incorrectly it throws an error. You would need to set up a try/catch statement to handle potential errors.
Steps to reproduce
Expected behavior
Please tell us about your environment
Node 16 SDK v1.14.0