Initially, the issue was reported for v17.11 and we fixed it in v18.10. We kept testing the scenario at our side but were unable to replicate it. The issue was happened to exist only in the case of multi-threading which was investigated and resolved. Would you kindly try using the latest available version of the API and let us know in case you are facing this issue still.