SessionStatus (FIX tag 1409)

intFIX 5.0 SP2

SessionStatus (tag 1409) is an int field defined in FIX 5.0 SP2. It appears in 2 message types, always optionally. It is an enumerated field with 9 defined values.

At a glance

Tag: 1409
Name: SessionStatus
Datatype: int
Dialects: FIX 5.0 SP2
Messages: 2
Valid values: 9

What the specification says

Status of a FIX session

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

A real message using tag 1409

Logon · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	88
35	MsgType	A	Logon Message
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
98	EncryptMethod	0	None
108	HeartBtInt	1
1409	SessionStatus	0	Session active
1137	DefaultApplVerID	9
10	CheckSum	122

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	Session active	SESSION_ACTIVE
1	Session password changed	SESSION_PASSWORD_CHANGED
2	Session password due to expire	SESSION_PASSWORD_DUE_TO_EXPIRE
3	New session password does not comply with policy	NEW_SESSION_PASSWORD_DOES_NOT_COMPLY_WITH_POLICY
4	Session logout complete	SESSION_LOGOUT_COMPLETE
5	Invalid username or password	INVALID_USERNAME_OR_PASSWORD
6	Account locked	ACCOUNT_LOCKED
7	Logons are not allowed at this time	LOGONS_ARE_NOT_ALLOWED_AT_THIS_TIME
8	Password expired	PASSWORD_EXPIRED

Where tag 1409 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
Logon	A	Optional	directly on the message body
Logout	5	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 1409 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 sessionStatus = message.fields[1409]?.raw;// e.g. "0" — Session active// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(1409)  ?.enumValues?.find((e) => e.value === sessionStatus)  ?.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