Junos will not generate a SNMP trap when a FPC prompts Major Errors

Chassisd logs will indicate logs such as the ones below:

HWMon: received one FPC alarm, reason 9, op 1
send: red alarm set, device FPC 10, reason FPC 10 Major Errors

The messages logs will not present any SNMP traps generated when the Major Errors alarms are present.
Example of messages logs;

Alarm set: FPC id=150995304, color=RED, class=CHASSIS, reason=FPC 10 Major Errors
Major alarm set, FPC 10 Major Errors

This is by design, the SNMP Traps will generate if there are any transitions from online/offline of the FPC
Example: https://apps.juniper.net/mib-explorer/navigate?software=Junos%20OS&release=23.2R1&name=jnxFruOffline&oid=1.3.6.1.4.1.2636.4.1.10

In order to generate a SNMP Trap an event-option configuration can be added:

a)a general alarm tram such as:

set event-options policy FPC-ALARM-TRAP events SYSTEM
set event-options policy FPC-ALARM-TRAP attributes-match system.message matches ".*alarm set.*"
set event-options policy FPC-ALARM-TRAP then raise-trap

b)or a more specific alarm for Major alarm:

set event-options policy FPC-ALARM-TRAP events SYSTEM
set event-options policy FPC-ALARM-TRAP attributes-match system.message matches ".*Major alarm set.*FPC.*"
set event-options policy FPC-ALARM-TRAP then raise-trap