SNMPTRAP not raised as alarms at OpManger due to exceptions

Hello

My service sends an SNMP TRAP to OpManager but the alarm is never raised.
We can see the TRAP in the MIBparser tool but not in the OpManager GUI (not in alarms).

Looking at the logs i saw that the nosuchinstance exceptions were raised due to the lack of 3 parameter in the trap.
Is it possible for OpManager to raise an alarm even if there are some exceptions??

Thanks
**************************************************************
E:193.19.3.4.2.3.3.1.4=[noSuchInstance]
E:193.19.3.4.2.3.3.1.8=[noSuchInstance]
E:193.19.3.4.2.3.3.1.9=[noSuchInstance]
************************************************************************

4:34:02:737 MISC: Trap Processing for v2 / v2c trap failed : .1.3.6.1.4.1.14574.1.1.3.2
14:34:02:737 MISC: Agent: 10.27.5.20
14:34:02:737 MISC: Varbinds: Object ID: .1.3.6.1.2.1.1.3.0
TimeTicks: 3 hours, 11 minutes, 14 seconds.
Object ID: .1.3.6.1.6.3.1.1.4.1.0
Object ID: .1.3.6.1.4.1.14574.1.1.3.2
Object ID: .1.3.6.1.4.1.193.19.3.4.2.3.3.1.6.10
STRING: 07 db 08 11 0d 22 04 00 2b 00 00
Object ID: .1.3.6.1.4.1.193.19.3.4.2.3.3.1.5.10
INTEGER: 2
Object ID: .1.3.6.1.4.1.193.19.3.4.2.3.3.1.3.10
Object ID: .1.3.6.1.4.1.14574.1.1
Object ID: .1.3.6.1.4.1.193.19.3.4.2.3.3.1.10.10
INTEGER: 10
Object ID: .1.3.6.1.4.1.193.19.3.4.2.3.3.1.11.10
INTEGER: 18859
Object ID: .1.3.6.1.4.1.193.19.3.4.2.3.3.1.12.10
INTEGER: 1
Object ID: .1.3.6.1.4.1.193.19.3.4.2.3.3.1.13.10
STRING:
Object ID: .1.3.6.1.4.1.193.19.3.4.2.3.3.1.7.10
STRING: {internal,{internal,session_navigation,session_crashed}}
Error Indication in response: There is no such instance in this MIB.Object ID: .1.3.6.1.4.1.193.19.3.4.2.3.3.1.4
NULLOBJ: NULL
Error Indication in response: There is no such instance in this MIB.Object ID: .1.3.6.1.4.1.193.19.3.4.2.3.3.1.8
NULLOBJ: NULL
Error Indication in response: There is no such instance in this MIB.Object ID: .1.3.6.1.4.1.193.19.3.4.2.3.3.1.9
NULLOBJ: NULL
Object ID: .1.3.6.1.4.1.193.19.3.4.2.2.1.1.1.9
INTEGER: 3