The bug is that transactions can be seen in "account_history.enum_virtual_ops" before the block they should enter is produced. The faulty virtual operations visible in "account_history_api" before the block is created have the number of the previous block. After the required block has been produced, the block number is changed to the correct one and the transaction is then displayed correctly afterwards.