Response action to message received with same MsgSeqNo and 43=Y

Imported from previous forum

Hi,

Following is the incidence sequence:

1 - VPN connection between both the sides is lost.
2 - After reconnection, SELL side requested ResendRequest.
3 - BUY side retransmitted order request with same sequence no. and 43 = Y. This message was not duplicate but tagged as PossibleDuplicate.
4 - Sell side ignored the order request since marked with 43=Y.

Is this a correct behavior as per FIX4.2 specification?

As per FIX 4.2 standards, in response to message received with ‘same sequence no. and 43= Y/N’ received from party responding to resend request, what should be the correct behavior of REQUESTER (party initiated the resend request) for

  1. Administrative messages with 43 = Y
  2. Administrative messages with 43 = N
  3. Application messages with 43 = Y
  4. Application messages with 43 = N

Thanks in advance.

Hi,

Following is the incidence sequence:

1 - VPN connection between both the sides is lost. 2 - After
reconnection, SELL side requested ResendRequest. 3 - BUY side
retransmitted order request with same sequence no. and 43 = Y. This
message was not duplicate but tagged as PossibleDuplicate. 4 - Sell side
ignored the order request since marked with 43=Y.

Is this a correct behavior as per FIX4.2 specification?

As per FIX 4.2 standards, in response to message received with ‘same
sequence no. and 43= Y/N’ received from party responding to resend
request, what should be the correct behavior of REQUESTER (party
initiated the resend request) for

  1. Administrative messages with 43 = Y
  2. Administrative messages with 43 = N
  3. Application messages with 43 = Y
  4. Application messages with 43 = N

Thanks in advance.

Administrative messages are never resent. The message of type 4 should be used instead.

An application should persist sequence numbers of incoming messages which have been processed. Therefore it should be able to decide if a resent message should be ignored (already processed) or not.