When I use aspose word cloud node, I often get the error ‘Unexpected token<in JSON at position 0.’ and occasionally get the error ‘aborted’. Please tell me the reason for this type of error, and I cannot rule out the specific reason.
And how can I view the interfaces that failed calls? I don’t see any failed calls on the dashboard, but in fact, 10% of my calls failed
I am afraid we have not noticed any such errors. Please ensure you are using the latest version of Aspose.Words Cloud SDK for Node. If the issue persists, then kindly share your sample script for investigation.
I am sure my version is the latest version, 23.3.0, but this error seems to occur randomly. There is a certain content that is bound to make such an error. This content will not make an error in your official website example, but calling the interface will inevitably make an error. I can test the content for you to see
Thanks for sharing the sample document. It seems to be a document related issue, as I am getting an ESOCKETTIMEDOUT error for the conversion. So I have logged a ticket (WORDSCLOUD-2322) for further investigation. We will notify you as soon as we fix the problem.
I have also encountered ESOCKETTIMEOUT errors, sometimes aborted, and most importantly, the error I frequently encounter is’ Unexpected token<in JSON at position 0. 'Please pay close attention to this
We have investigated the WORDSCLOUD-2322 issue and noticed that example.html contains a lot of links to external resources that are causing the ESOCKETTIMEDOUT error.
Please note that the Words Cloud API is forbidden from using data from the internet; it uses data stored on internal storage only. Please remove all the links to external resources. If you need some additional files, load them too. But please ensure that the additional files don’t have external links.
Please note that we don’t have any limitations on file size, but each container(node) has limited memory. Memory consumption depends upon the file structure, as sometimes a 10MB file can take 1GB in memory while processed, and 100MB can take from 100MB to a huge number. You can try the conversion with your big flies; however, if you face any issues, you can share your input document via some free file sharing service with us for investigation.