CxlRejReason (FIX tag 102)

intFIX 4.4FIX 4.2

CxlRejReason (tag 102) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 1 message type, always optionally. It is an enumerated field with 8 defined values.

At a glance

Tag: 102
Name: CxlRejReason
Datatype: int
Dialects: FIX 4.4 and FIX 4.2
Messages: 1
Valid values: 8

What the specification says

FIX 4.4

Code to identify reason for cancel rejection

FIX 4.2

Code to identify reason for cancel rejection.

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

A real message using tag 102

OrderCancelReject · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	119
35	MsgType	9	Order Cancel Reject
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
11	ClOrdID	ORD-10042
41	OrigClOrdID	ORD-10041
39	OrdStatus	0	New
434	CxlRejResponseTo	1	Order Cancel Request
102	CxlRejReason	0	Too late to cancel
10	CheckSum	211

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 4.4 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	Dialects
0	Too late to cancel	TOO_LATE_TO_CANCEL / TooLateToCancel	FIX 4.4, FIX 4.2
1	Unknown order	UNKNOWN_ORDER / UnknownOrder	FIX 4.4, FIX 4.2
2	Broker / Exchange Option	BROKER / BrokerCredit	FIX 4.4, FIX 4.2
3	Order already in Pending Cancel or Pending Replace status	ORDER_ALREADY_IN_PENDING_CANCEL_OR_PENDING_REPLACE_STATUS / OrderAlreadyInPendingStatus	FIX 4.4, FIX 4.2
4	Unable to process Order Mass Cancel Request	UNABLE_TO_PROCESS_ORDER_MASS_CANCEL_REQUEST	FIX 4.4
5	OrigOrdModTime (586) did not match last TransactTime (60) of order	ORIGORDMODTIME	FIX 4.4
6	Duplicate ClOrdID (11) received	DUPLICATE_CLORDID	FIX 4.4
99	Other	OTHER	FIX 4.4

Where tag 102 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	FIX 4.4	FIX 4.2	Where in the message
OrderCancelReject	9	Optional	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 102 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const cxlRejReason = message.fields[102]?.raw;// e.g. "0" — Too late to cancel// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(102)  ?.enumValues?.find((e) => e.value === cxlRejReason)  ?.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-fix44

Try the decoder Source on GitHub