branch null was marked as FAILED - flow execution with random error

Has someone experienced an error like this?

Server.log -->

2019-11-22 06:32:47,852 [https-jsse-nio-443-exec-9] (FailedFlowsHandler.java:92) WARN - Execution 513918404 branch null was marked as FAILED due to RuntimeException. Terminating this execution.
2019-11-22 09:34:47,772 [https-jsse-nio-443-exec-2] (FailedFlowsHandler.java:92) WARN - Execution 513922203 branch null was marked as FAILED due to RuntimeException. Terminating this execution.

We have some scheduled flows running every minute and this failure presents randomly, maybe a resources issue, jvm or tomcat config starting from a fresh install? The flow's actions are, depending on some conditions, call 2 rest api endpoints and get/send some payload.

We have a dedicated alias group for this executions, 4 GB RAM, 200 workers and 1500 buffer size in wrapper. Tomcat config hasn't been modified.

MSSQL 2016 database for more information.

Thanks!FlowException.PNG

  • Probabely it had some thing to do with your RAS <-> Central --> MSSQL connections.

    Is there any network disturbance between the RAS and Central or the Central and DB when the issue occurs?

    If not, you may need to monitor the database connections number from OO to the database when this issue occurs, and cross check with the <OO Central DIR>\central\conf\database.properties, as well as the connection limit set in the MSSQL instance.

  • If any of you experience this problem with a clustered installation, it's an issue related to a table purge (running exec configs). I opened a case and they provided me with the hotfix. The definitive solution was implemented in version 2019.07