The order has been removed since the subaccount does not satisfy the equity tier requirements.

The order was removed due to being expired.

The order has been removed since its ClobPair has entered final settlement.

The order was a fill-or-kill order that could not be fully filled and was removed.

The order has been fully-filled.

The order was an ICO order and would have been placed on the orderbook as resting liquidity and was removed.

The order should be expired, according to the Indexer's cached data, but the Indexer has yet to receive a message to remove the order.

The order caused an internal error during order placement and was removed.

The order would have matched against maker orders on the orderbook despite being a post-only order and was removed.

The order was a reduce-only order that was removed due to either: - being a taker order and fully-filling the order would flip the side of the subaccount's position, in this case the remaining size of the order is removed - being a maker order resting on the book and being removed when either the subaccount's position is closed or flipped sides.

The order has been replaced.

The order would have matched against another order placed by the same subaccount and was removed.

The order was removed due to being undercollateralized.

Default value, this is invalid and unused.

The order was removed due to being canceled by a user.

The order has been removed since filling it would lead to the subaccount violating isolated subaccount constraints.

OrderRemovalReason is an enum of all the reasons an order was removed.