RE: Sometimes we have processes that stop executing because of database connectivity

Chris — Tue, 25 Mar 2014 01:07:44 GMT

To find broken processes, we use a report for all models and filter on 0 active tasks (num_active_tasks()=0). This does a pretty good job, but doesn't catch the scenerios where you have 2 tasks active at once (and one could be broken) or processes holding intentionally, etc.

For mass re-starts, I began setting all DB nodes to false() for 'Pause on Error'. The error flag is recorded, and if the connection was not successful the process sends an alert to the developers group (with the error message) and waits at a Recieve Message node. Once the DB is back online, I run a process model (DB Restarts) that sends a message to all processes to release the hold. This works fantastic - this week we had 100 broken processes due to a connection failure, and it took me less than 1 minute to browse to the restart model, fire it off, and all processes resumed.

RE: Sometimes we have processes that stop executing because of database connectivity

ryanh — Mon, 24 Mar 2014 22:37:37 GMT

...toring, finding the node, cancelling it and restarting it is rather time consuming and prone to user errors.

Ryan