On 19/Feb/2024 a client reported in the support-forum that the execution of his app ended up in an ERROR status, even if the execution looked successful and all the expected outputs were generated.
It turned out that the ERROR state was caused by the running time exceeding the app's time out.
In that case, however, the status should have been STOPPED and not ERROR. We should check why the correct state was not set for the app.
On 19/Feb/2024 a client reported in the support-forum that the execution of his app ended up in an ERROR status, even if the execution looked successful and all the expected outputs were generated.
It turned out that the ERROR state was caused by the running time exceeding the app's time out. In that case, however, the status should have been STOPPED and not ERROR. We should check why the correct state was not set for the app.
The logs are available at this link (access restricted to WASDI group on Drive): https://drive.google.com/file/d/1SrJzG7HX9cYD7xhk4pTjgOR0Bo-yHqWP/view?usp=sharing