PB 2017 R3, PostgreSQL 11.1
Looks like PB doesn't report an error when there is a violation of uniquess in a table, instead it goes into a infinite loop. Uniqueness created with a unique index and NOT primary key.
Removing the unique index, solves this issue.
Have anyone faced this issue before ?