You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if there is a way to know that the execution has stopped due to the timeout? I am not sure if it already exists and it would be helpful if we have one.
The text was updated successfully, but these errors were encountered:
In the latest version it doesn't appear to be documented but I found that when the run.status = "TO" the execution has been terminated because of timeout and if it is "XX" it is because of exceeding the output limit.
According to the documentation of the latest version, XX is used for reporting internal errors so it should not be relied on for determining if the output limits were exceeded. I have made a PR that sets an appropriate status for exceeding the output limits, and also reports SIGKILL when the time-limit or the output limit is exceeded to maintain backward compatibility.
I was wondering if there is a way to know that the execution has stopped due to the timeout? I am not sure if it already exists and it would be helpful if we have one.
The text was updated successfully, but these errors were encountered: