Possible Idempotency Issue while sending many transactions with same TxId - v1.3

CASE 1 - Idempotency is preserved   1.1) Generate the TransactionID by calling "Client.newTransactionID()"   1.2) Call "invoke" method   1.3) Wait for the transaction to be validated   1.4) Try to perform an "invoke" with the same TransactionID from step "1.1)" - Idempotency preserved     CASE 2 - Idempotency is not preserved (strange behavior)   2.1) Generate the TransactionID by calling "Client.newTransactionID()"   2.2) Call "invoke" the chaincode multiple times, with the same TransactionID, before any of the transactions has time to be committed.   2.3) Consult the status of the Ledger by "query" method. (In the Ledger state, all generated transaction states in step "2.2)" have been saved in CouchDB) - Idempotency not preserved. The same TransactionId produced several changes in the World State.   2.4) See "Channel.queryTransaction(tx_id)". The transaction returned by the Ledger contains the payload of only one of the submitted transactions - Strange behavior