releaselock status in web_api_details.csv

Looking at the releaselock definition here, I don't believe it's an issue unless you're seeing the corresponding TypeError signifying a read request is still pending.

As for changing the logging times, I'm not sure this is possible, however you should be able to reference the application server logs for any errors that are generated during your testing, and you could turn on DEBUG logging for more information details.

Looking at the releaselock definition here, I don't believe it's an issue unless you're seeing the corresponding TypeError signifying a read request is still pending.

As for changing the logging times, I'm not sure this is possible, however you should be able to reference the application server logs for any errors that are generated during your testing, and you could turn on DEBUG logging for more information details.

Thanks coltonb, 100 transactions calls the web api at the same time. As expected should receive a response from the appian web api. But after running the test, there are some transactions that didn't get a response.