BDR - Ignore already exists error during DDL replay

Hello,

In my 2-node BDR setup if I make changes in db schema I am seeing below
error or after few reboots I get into below inconsistent state during DDL
replay. Is there any way to ignore ItemAlreadyExists error during DDL
replay ?

global lock of DDL replication is switched off in configuration.

Best Regards,
Nikhil

GMT%ERROR: trigger "truncate_trigger" for relation
"provisionsettings_server_boundary" already e
xists
<283032016-07-12 15:51:58 GMT%CONTEXT: during DDL replay of ddl statement:
CREATE TRIGGER truncate_trigger AFTER TRUNCATE
ON public.provisionsettings_server_boundary FOR EACH STATEMENT EXECUTE
PROCEDURE bdr.queue_truncate()
<3662016-07-12 15:51:58 GMT%LOG: worker process: bdr
(6306146678097036401,2,16386,)->bdr (6306138636064436461,1, (PID 2830
3) exited with exit code 1