Zipline treats “Inactive” orders as still being open, with the possibility of becoming active again. This interpretation is based on the IBKR API docs. However, the IBKR API seems to contradict the docs, because the API does not send back “inactive” orders when you request all open orders. Based on this evidence, I think it would be more accurate for Zipline to treat inactive orders as cancelled.
We will make this change in the next release. For now, the easiest workaround would be to manually change "Inactive" to "Cancelled" at the database level (please backup the database before making manual edits):
sqlite3 /var/lib/quantrocket/quantrocket.v2.blotter.statuses.sqlite 'UPDATE OrderStatus SET Status = "Cancelled" WHERE Status = "Inactive"'