# 3391 ERROR Triggers Consuming Exceptions Even When WHEN Clause Evaluates to False

---

We have ERROR ALL triggers with a condition of LOADINGUPDATES() on our tables to trap replication errors. However, with these in place, it appears that primary key constraint errors during normal program operation are not being thrown any more. Instead of generating an error, the active record is changed to the original row with the duplicate primary key. In the code, we are wrapping table posting in try/catch blocks and we are never notified that an error occurred.