Persistent and non-persistent orders

Orders can be entered as persistent or as non-persistent orders. Persistent orders are persisted in a database of T7. This prevents persistent orders from being lost in case of a technical system failure. During the restart after a system failure, T7 re-loads the persistent orders from the database. The priority time stamp of these orders remains unchanged. 

Non-persistent orders are automatically deleted as soon as a trading interruption occurs in the corresponding instrument. From a participant’s point of view non-persistent orders always offer clarity as regards their status in the event of trading interruptions or technical problems.

Lean orders

For orders flag as “lean”, the receipt of status information messages is restricted to the session, through which the order had been entered. Furthermore, only such information messages may be recovered via a retransmission request that is about executions and about events, which were not solicited by the owner of the order. For an order that is not flagged as a lean order, the receipt of status information messages is not restricted to the session, through which the order had been entered, and information messages about all events regarding the order may be recovered via a retransmission request.

T7 does not accept orders that are both lean and persistent. Orders that are entered through a high-frequency session may be persistent or non-persistent.