Could depend on how your event is configured.

If you set it to run BEFORE the write to the table, you could then prevent it from completing the write, depending on what you event/action was defined to do.

Nick

Hi Nick. Thanks for the response. 
 

the event is set to trigger after a new record is created. 

Could there be some sort of failsafe against recursive effects? If your event does something that writes to a table with history logging turned on, your event could cause an infinite loop, no? Not sure how IFS would know that, though, unless Oracle has built-in circular reference checks.

Joe Kaufman

Hi Joe,

I did think they initially, however I checked this by creating a custom LU and updating that instead. Custom LU didn’t have logging on and still the same issue

I am having the same issue so I’m also interested if someone has a solution for this :)

Hi @MitJamieB 

Please check predefined event: HISTORY_LOG_MODIFIED. Try this achive your goal.

“After” triggers will still cause the whole transaction to fail if something goes wrong. If you feel comfortable posting your event action code, we might be able to help you more.