Hi @mohamed3nan , hi @darrell_tw
Thank you for your inputs and help.
I spent the whole day today running numerous tests and investigating everything with my app programmer. We discovered an irregularity in the process on our app that accesses external data links from Heygen after the API call.
We discovered that Heygen requires different runtimes to generate the various retrieval links. When it took a little longer for some of the URLs to be completed, the variables in our database remained empty and were returned as “NULL” in the response, without quotes, thus generating invalid JSON.
We’ve now placed a 30-second wait node between the Heygen request and the request to the KLINK app to ensure that the information is provided by Heygen. We encountered one error at 20 seconds in our tests.
After 40 test rounds, things are looking good, and we’re confident that was the cause.