This is a bug that causes an exception for sending a second transaction when using a high-performance wallet.
The reason for this is that the wrong queryId is being used, as can be seen in the contract code at https://github.com/ton-blockchain/ton/blob/master/crypto/smartcont/highload-wallet-v2-code.fc, which handles the timestamp as The processing of the timestamp is shifted 32 bits to the left, not 32 times, which currently causes it to be out of range for the long type, and the queryId is always the maximum value for the long type, i.e. 9223372036854775807
This is a bug that causes an exception for sending a second transaction when using a high-performance wallet.
The reason for this is that the wrong queryId is being used, as can be seen in the contract code at https://github.com/ton-blockchain/ton/blob/master/crypto/smartcont/highload-wallet-v2-code.fc, which handles the timestamp as The processing of the timestamp is shifted 32 bits to the left, not 32 times, which currently causes it to be out of range for the long type, and the queryId is always the maximum value for the long type, i.e. 9223372036854775807