# Error handling for OrderStatusRequest **URL:** \ **Category:** General Q&A\ **Tags:** general-qa, xid\_167909, imported\ **Created:** [December 9, 2009, 3:37pm UTC](https://forum.fixtrading.org/t/error-handling-for-orderstatusrequest/4957 "2009-12-09T15:37:41Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![eriknyquist\_x](https://avatars.discourse-cdn.com/v4/letter/e/7c8e57/32.png) [@eriknyquist\_x](https://forum.fixtrading.org/u/eriknyquist_x)\ **Post date:** [December 9, 2009, 3:37pm UTC](https://forum.fixtrading.org/t/error-handling-for-orderstatusrequest/4957/1 "2009-12-09T15:37:41Z")
Imported from previous forum ---
**Author:** ![eriknyquist\_x](https://avatars.discourse-cdn.com/v4/letter/e/7c8e57/32.png) [@eriknyquist\_x](https://forum.fixtrading.org/u/eriknyquist_x)\ **Post date:** [December 9, 2009, 3:37pm UTC](https://forum.fixtrading.org/t/error-handling-for-orderstatusrequest/4957/2 "2009-12-09T15:37:41Z")
If I send an OrderStatusRequest(H) (FIX 5.0 SP1) containing a ClOrdID that does not exist or refers to an order that I have not permission to see, what is the expected behavior of the FIX gateway? Which of these possible strategies should we consider: 1. Ignore the request 2. Return an ExecutionReport having ExecType=I (Status Request) 3. Return an ExecutionReport having ExecType=8 (Rejected) I have not been able to find any guidelines in the FIX spec. So what do you think? /Erik ---
**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\ **Post date:** [December 10, 2009, 3:48am UTC](https://forum.fixtrading.org/t/error-handling-for-orderstatusrequest/4957/3 "2009-12-10T03:48:42Z")
[original email was from Harish Kamaley - [harish.kamaley@wipro.com](mailto:harish.kamaley@wipro.com) ] Return an Execution Report 35=8 with following tags 150=I(Status) 39=8(Reject) 103=5(Unknown Order) 17=0 38=0 14=0 151=0 6=0 Please refer: fix-43\_VOL-4\_with\_Errata\_20020920.doc page no. 69, Order State Change Matrices, D29 Regards Harish > If I send an OrderStatusRequest(H) (FIX 5.0 SP1) containing a ClOrdID > that does not exist or refers to an order that I have not permission to > see, what is the expected behavior of the FIX gateway? > > Which of these possible strategies should we consider: > > 1. Ignore the request > > 2. Return an ExecutionReport having ExecType=I (Status Request) > > 3. Return an ExecutionReport having ExecType=8 (Rejected) > > I have not been able to find any guidelines in the FIX spec. > > So what do you think? > > /Erik ---
**Author:** ![eriknyquist\_x](https://avatars.discourse-cdn.com/v4/letter/e/7c8e57/32.png) [@eriknyquist\_x](https://forum.fixtrading.org/u/eriknyquist_x)\ **Post date:** [December 10, 2009, 9:40am UTC](https://forum.fixtrading.org/t/error-handling-for-orderstatusrequest/4957/4 "2009-12-10T09:40:47Z")
Thanks a lot. For FIX 5.0 SP1, the same info can be found in the FIX-5.0\_SP1\_VOL-4.doc document at page 82. The spec is a bit contradictionary when it describes the purpose of OrdRejReason (103). This is what the spec above says at page 18: 103, OrdRejReason, For optional use with ExecType = 8 (Rejected). Shouldn’t this say? For optional use with ExecType = 8 (Rejected) or ExecType = I (Status) /Erik > Return an Execution Report 35=8 with following tags 150=I(Status) > 39=8(Reject) 103=5(Unknown Order) 17=0 38=0 14=0 151=0 6=0 > > Please refer: fix-43\_VOL-4\_with\_Errata\_20020920.doc page no. 69, Order > State Change Matrices, D29 > > Regards Harish > > > If I send an OrderStatusRequest(H) (FIX 5.0 SP1) containing a ClOrdID > > that does not exist or refers to an order that I have not permission > > to see, what is the expected behavior of the FIX gateway? > > > > Which of these possible strategies should we consider: > > > > 1. Ignore the request > > > > 2. Return an ExecutionReport having ExecType=I (Status Request) > > > > 3. Return an ExecutionReport having ExecType=8 (Rejected) > > > > I have not been able to find any guidelines in the FIX spec. > > > > So what do you think? > > > > /Erik ---
**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\ **Post date:** [December 10, 2009, 10:58am UTC](https://forum.fixtrading.org/t/error-handling-for-orderstatusrequest/4957/5 "2009-12-10T10:58:15Z")
[original email was from Bivas Mishra - [bivas.mishra@wipro.com](mailto:bivas.mishra@wipro.com) ] Hi, Unless the specs need a relook for usage of Tag 103, the alternative way to respond could be thus: (150)ExecType=(I)Status Ignore populating (103)OrdrejReason and provide a text in Tag 58 stating the reason that clOrdId not found. Regards. > Thanks a lot. For FIX 5.0 SP1, the same info can be found in the FIX-5.0\_SP1\_VOL- > 4.doc document at page 82. > > The spec is a bit contradictionary when it describes the purpose of > OrdRejReason (103). This is what the spec above says at page 18: > > 103, OrdRejReason, For optional use with ExecType = 8 (Rejected). > > Shouldn’t this say? > > For optional use with ExecType = 8 (Rejected) or ExecType = I (Status) > > /Erik > > > Return an Execution Report 35=8 with following tags 150=I(Status) > > 39=8(Reject) 103=5(Unknown Order) 17=0 38=0 14=0 151=0 6=0 > > > > Please refer: fix-43\_VOL-4\_with\_Errata\_20020920.doc page no. 69, Order > > State Change Matrices, D29 > > > > Regards Harish > > > > > If I send an OrderStatusRequest(H) (FIX 5.0 SP1) containing a > > > ClOrdID that does not exist or refers to an order that I have not > > > permission to see, what is the expected behavior of the FIX gateway? > > > > > > Which of these possible strategies should we consider: > > > > > > 1. Ignore the request > > > > > > 2. Return an ExecutionReport having ExecType=I (Status Request) > > > > > > 3. Return an ExecutionReport having ExecType=8 (Rejected) > > > > > > I have not been able to find any guidelines in the FIX spec. > > > > > > So what do you think? > > > > > > /Erik