Fact Plugin throws an exception SOSHibernateQueryException when SQL query fails

Current Situation
The DailyPlan running in the Fact Plugin throws an exception com.sos.hibernate.exceptions.SOSHibernateQueryException when there is a transaction and one of the SQL Queries failed. This failure gets ignored and the same connection and transaction are used to run another query. The second statement then throws the exception because a broken transaction is used to execute it.

 Desired Behaviour
When the SQL Queries failed and if the same connection is used then JobScheduler should not throw the exception com.sos.hibernate.exceptions.SOSHibernateQueryException