Any way to trap a DB Connection Error when running a QueryEntity Rule? I am popu

I do not know of any way to achieve that. If SQL is OK for you then you could use the "Query Database" smart service. It can be configured to not halt on errors but returns an error flag you could react on.

Can you explain your use case?

I thought of that but thanks for the input. It just seemed to silly to add the DB node to do a connection check if there was an easier way. I am calling a view which calls a separate DB. If they take it down for maintenance I didn't want the process to require manual intervention to restart nodes. It seems like the queryEntity function should accommodate for SQL errors code returns but I wasn't able to see a way.

As far as I know, there is no direct way to trap the DB connection errors, we can wrap the script task which calls the QueryEntity rule in PM, use new PM as a subprocess and configure exception flow for the subprocess. This exception flow can be timer bassed. Take the exception flow can be used do necessary steps (Sending email/alert or retrying)