Wallet TXN not found within timeout

[Snipa22]

Describe the bug
During a TXN send via GRPC, the wallet can respond with a TXN not found within timeout, even when the TXN is successfully created and sent via the base node

To Reproduce
Steps to reproduce the behavior:
Send transactions via the wallet, I'm sending ~700 at a time with a pool of 4000 UTXO's, and this is occouring when i do the TXN's sequentially, as well as using 100-out groups.

Expected behavior
I expect the wallet to properly respond on the GRPC if a TXN is sent and submitted to the base_node, and there by network.

Server (please complete the following information):
Debian 13
minotari_console_wallet 5.3.1

Additional context

GRPC/Payout logs:

time="2026-05-26T16:00:03Z" level=info msg="rpc error: code = NotFound desc = Transaction 2013336255742160387 not found within timeout"
time="2026-05-26T16:00:03Z" level=error msg="Dumping all data in the transaction struct for debugging"
time="2026-05-26T16:00:03Z" level=error msg="Batch: 3 Index: 0, data: address:\"REDACTED\"  amount:REDACTED  fee_per_gram:5  payment_type:ONE_SIDED"
time="2026-05-26T16:00:03Z" level=info msg="Processed batch WITH ERROR: 3/732"

Wallet Logs:

base_layer.log:18395:2026-05-26 16:00:02.737439038 [wallet::transaction_service::service] [Thread:139718003979968] INFO  Finalized one-side transaction TxId: 2013336255742160387
base_layer.log:18396:2026-05-26 16:00:02.737520759 [wallet::output_manager_service::database::wallet] [Thread:139718003979968] DEBUG Replacing temp tx_id in outputs '3146959716295325831' with '2013336255742160387'
base_layer.log:18397:2026-05-26 16:00:02.897364429 [wallet::transaction_service::protocols] [Thread:139718003979968] DEBUG Transaction '2013336255742160387' size ok, can be broadcast (got: 3422, limit: 4184064).
base_layer.log:18398:2026-05-26 16:00:02.905307527 [wallet::transaction_service::protocols] [Thread:139714501711552] DEBUG Transaction '2013336255742160387' size ok, can be broadcast (got: 3422, limit: 4184064).
base_layer.log:18399:2026-05-26 16:00:02.905362988 [wallet::transaction_service::protocols::broadcast_protocol] [Thread:139714501711552] INFO  Submitting Transaction (TxId: 2013336255742160387) with signature 'cbee6458f77c8e0a0575fd3b4da8752abecaa50fa6d41d15a5e5ee56c4873109' to Base Node
base_layer.log:18400:2026-05-26 16:00:02.911161418 [wallet::transaction_service::protocols::broadcast_protocol] [Thread:139714501711552] INFO  Transaction (TxId: 2013336255742160387) submission response from Base Node: TxSubmissionResponse { accepted: true, rejection_reason: None, is_synced: true }
base_layer.log:18401:2026-05-26 16:00:02.911177439 [wallet::transaction_service::protocols::broadcast_protocol] [Thread:139714501711552] INFO  Transaction (TxId: 2013336255742160387) successfully submitted to UnconfirmedPool
base_layer.log-18402-2026-05-26 16:00:02.967252710 [wallet::ui::grpc] [Thread:139718003979968] DEBUG GetCompletedTransactions: Found 0 completed transactions
base_layer.log:18403:2026-05-26 16:00:03.068529806 [wallet::ui::grpc] [Thread:139718003979968] ERROR Transaction 2013336255742160387 not found within timeout
base_layer.log:18404:2026-05-26 16:00:03.301406021 [wallet::transaction_service::service] [Thread:139719883790016] WARN  Failed to send reply: Ok(AnyTransaction(Some(Completed(CompletedTransaction { tx_id: TxId(2013336255742160387), source_add
base_layer.log-19104-2026-05-26 16:00:23.170270953 [wallet::transaction_service::protocols::validation_protocol] [Thread:139719883790016] INFO  Asking base node for location of 20 transactions by excess signature (Operation ID: 12329155456567530581)
base_layer.log:19105:2026-05-26 16:00:23.170806172 [wallet::transaction_service::protocols::validation_protocol] [Thread:139719883790016] WARN  Transaction 2013336255742160387 is unmined (Operation ID: 12329155456567530581)
base_layer.log-19106-2026-05-26 16:00:23.171545775 [wallet::transaction_service::protocols::validation_protocol] [Thread:139719883790016] WARN  Transaction 18309175103173524668 is unmined (Operation ID: 12329155456567530581)
base_layer.log-19107-2026-05-26 16:00:23.171760679 [wallet::transaction_service::protocols::validation_protocol] [Thread:139719883790016] WARN  Transaction 1169672242552790670 is unmined (Operation ID: 12329155456567530581)
base_layer.log-19108-2026-05-26 16:00:23.171970632 [wallet::transaction_service::protocols::validation_protocol] [Thread:139719883790016] WARN  Transaction 15680789863287678814 is unmined (Operation ID: 12329155456567530581)
--
base_layer.log-19123-2026-05-26 16:00:23.174613318 [wallet::transaction_service::protocols::validation_protocol] [Thread:139719883790016] WARN  Transaction 639660147493852129 is unmined (Operation ID: 12329155456567530581)
base_layer.log-19124-2026-05-26 16:00:23.174768031 [wallet::transaction_service::protocols::validation_protocol] [Thread:139719883790016] WARN  Transaction 1356380553762619300 is unmined (Operation ID: 12329155456567530581)
base_layer.log-19125-2026-05-26 16:00:23.174775821 [wallet::transaction_service::protocols::validation_protocol] [Thread:139719883790016] DEBUG Base node returned 0 as mined and 20 as unmined (Operation ID: 12329155456567530581)
base_layer.log:19126:2026-05-26 16:00:23.174779341 [wallet::transaction_service::protocols::validation_protocol] [Thread:139719883790016] DEBUG Updated transaction 2013336255742160387 as unmined (Operation ID: 12329155456567530581)
base_layer.log-19127-2026-05-26 16:00:23.245752701 [wallet::transaction_service::protocols] [Thread:139714514319040] DEBUG Transaction '9240155803064332766' size ok, can be broadcast (got: 4255, limit: 4184064).
base_layer.log:24838:2026-05-26 16:03:03.218500277 [wallet::transaction_service::protocols] [Thread:139714501711552] DEBUG Transaction '2013336255742160387' size ok, can be broadcast (got: 3422, limit: 4184064).
base_layer.log:24839:2026-05-26 16:03:03.218532007 [wallet::transaction_service::protocols::broadcast_protocol] [Thread:139714501711552] INFO  Querying Transaction (TxId: 2013336255742160387) status on Base Node
base_layer.log:24840:2026-05-26 16:03:03.219448233 [wallet::transaction_service::protocols::broadcast_protocol] [Thread:139712379442880] INFO  Transaction (TxId: 2013336255742160387) found in mempool.

Continues on with standard mempool and txn send bits. This is a high priority issue as the GRPC tells the application that the TXN failed, but it's actually sent funds and succeeded. This is particularly an issue for multi-out txns, because the /entire/ batch is seen to fail, even though funds were sent to some of the addresses in the batch.

[SWvheerden]

the latest build clears up somewhat whats going on here, its to due with a timeout and db issues.
The wallet does this:

1. build tx
2. submit tx
3. wait for submit

On step 3 is where the issue is, its timeing out while awaiting submit.
The latest build will tell you the tx is done and built, but that it does not have the submit results yet,
But I can see if this can be optimised.

Are you running batch tx with single_tx = true?

[Snipa22]

No, I'm still using the old Transfer method where it builds a number of txns using utxos per txn. I've meant to change over, it's on my todo list at some point. I've shifted to sending 1 txn in a batch to limit the impact of this (SXMR paid out the same balances multiple times because the wallet reported the txn was in a failed state due to being unable to find it in time, which we interpert (Validly, in the past), as the entire txn batch had failed. Has the structure for how txns are sent changed in the last few versions?

Also, we're on latest published (5.3.1), unless you mean a beta branch.

[SWvheerden]

I am talking beta branch here: https://github.com/tari-project/tari/releases/tag/v5.4.0-pre.0
Its just a reporting change so you know if the actual txn failed, or its just a broadcast issue, before 5.4.0 it would report any failure as a complete failure