The profile for an active cluster sometimes can not be read

Current Situation

When switching to an active cluster an error message

JOC-420
org.hibernate.exception.ConstraintViolationException: could not execute statement

might appear.

The reason for this is that it could happen that for each cluster member there are records with different accounts. As the profile is readed with the scheduler_instance_id (and the instance_id is not defined as there are several cluster members) and not with the scheduler id the resultlist could be empty and JOC tries to insert a new record. As there is a unique constraint the insert fails.

Desired Behaviour

The webservice url /configurations should read the list of configurations using the scheduler_id and not using the instance_id.