when "ERROR: broadcast_tx_commit: Response error: RPC error -32603 - Internal error: Timed out waiting for tx to be included in a block"

[iammelea]

After made one TX the output =
ERROR: broadcast_tx_commit: Response error: RPC error -32603 - Internal error: Timed out waiting for tx to be included in a block

have to be better explained and its not one error because the TX is not killed and is still in cache.
Example
Wait: broadcast_tx_commit: waiting for tx to be included in a block

because
I can understand after read
ERROR: broadcast_tx_commit: Response error: RPC error -32603 - Internal error: Timed out waiting for tx to be included in a block

and see the process is killed, that the TX is killed too and i can try to do the same TX again.

then if the TX is in cache i can read the output from this next TX

ERROR: broadcast_tx_commit: Response error: RPC error -32603 - Internal error: Error on broadcastTxCommit: Tx already exists in cache

But if i am slow and send another tx after the old is out from cache. i can do the same TX two times when i just need do it one time.

This can be fixed just changed the output when the TX is waiting to be validate.

thanks

[fedekunze]

I believe this issue is solved. Please reopen if you're able to reproduce the bug

[alexanderbez]

We still need a better mempool UX...probably something that will come out of moving the mempool to the application side. Regardless, txs are broadcasted in sync mode by default and block should never really be used.