MassActionRejectReason (FIX tag 1376)

intFIX 5.0 SP2

MassActionRejectReason (tag 1376) is an int field defined in FIX 5.0 SP2. It appears in 1 message type, always optionally. It is an enumerated field with 13 defined values.

At a glance

Tag: 1376
Name: MassActionRejectReason
Datatype: int
Dialects: FIX 5.0 SP2
Messages: 1
Valid values: 13

What the specification says

Reason Order Mass Action Request was rejected

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 1376

OrderMassActionReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	105
35	MsgType	BZ	OrderMassActionReport
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
1369	MassActionReportID	EXAMPLE
1373	MassActionType	1	Suspend orders
1374	MassActionScope	1	All orders for a security
1375	MassActionResponse	0	Rejected - See MassActionRejectReason(1376)
1376	MassActionRejectReason	0	Mass action not supported
10	CheckSum	170

Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

Value	Meaning	Symbolic name
0	Mass action not supported	MASS_ACTION_NOT_SUPPORTED
1	Invalid or unknown security	INVALID_OR_UNKNOWN_SECURITY
2	Invalid or unknown underlying security	INVALID_OR_UNKNOWN_UNDERLYING_SECURITY
3	Invalid or unknown product	INVALID_OR_UNKNOWN_PRODUCT
4	Invalid or unknown CFI Code	INVALID_OR_UNKNOWN_CFICODE
5	Invalid or unknown security type	INVALID_OR_UNKNOWN_SECURITYTYPE
6	Invalid or unknown trading session	INVALID_OR_UNKNOWN_TRADING_SESSION
7	Invalid or unknown market	INVALID_OR_UNKNOWN_MARKET
8	Invalid or unknown market segment	INVALID_OR_UNKNOWN_MARKET_SEGMENT
9	Invalid or unknown security group	INVALID_OR_UNKNOWN_SECURITY_GROUP
10	Invalid or unknown issuer	INVALID_OR_UNKNOWN_SECURITY_ISSUER
11	Invalid or unknown issuer of underlying security	INVALID_OR_UNKNOWN_ISSUER_OF_UNDERLYING_SECURITY
99	Other	OTHER

Where tag 1376 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

Message	MsgType	Requiredness	Where in the message
OrderMassActionReport	BZ	Optional	directly on the message body

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 1376 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const massActionRejectReason = message.fields[1376]?.raw;// e.g. "0" — Mass action not supported// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(1376)  ?.enumValues?.find((e) => e.value === massActionRejectReason)  ?.description;

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix50sp2

Try the decoder Source on GitHub