# Error message for new trade in 1.3

**URL:** <https://bisq.community/t/error-message-for-new-trade-in-1-3/9245>\
**Category:** Uncategorized\
**Created:** [April 8, 2020, 8:24pm UTC](https://bisq.community/t/error-message-for-new-trade-in-1-3/9245 "2020-04-08T20:24:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![decentralizedArtist](https://bisq.community/letter_avatar/decentralizedartist/32/6_22734026db12803ebb3e059622ac3534.png) [@decentralizedArtist](https://bisq.community/u/decentralizedArtist)\
**Post date:** [April 8, 2020, 8:24pm UTC](https://bisq.community/t/error-message-for-new-trade-in-1-3/9245/1 "2020-04-08T20:24:11Z")

</div>

An error occured at task: BuyerVerifiesFinalDelayedPayoutTx  
DelayedPayoutTx is not spending depositTx correctly

Since upgrading to 1.3 I’m getting Error messages for all previously (1.29) opened and newly opened trades. I’m reluctant to open Support tickets and mediator disputes… should I just let the trades ride and wait for the 1.31 upgrade?

---

<div class="post-metadata">

**Author:** ![huey](https://bisq.community/letter_avatar/huey/32/6_22734026db12803ebb3e059622ac3534.png) [@huey](https://bisq.community/u/huey)\
**Post date:** [April 8, 2020, 8:30pm UTC](https://bisq.community/t/error-message-for-new-trade-in-1-3/9245/2 "2020-04-08T20:30:07Z")

</div>

Yes, do wait for the next update.

---

<div class="post-metadata">

**Author:** ![decentralizedArtist](https://bisq.community/letter_avatar/decentralizedartist/32/6_22734026db12803ebb3e059622ac3534.png) [@decentralizedArtist](https://bisq.community/u/decentralizedArtist)\
**Post date:** [April 8, 2020, 8:51pm UTC](https://bisq.community/t/error-message-for-new-trade-in-1-3/9245/3 "2020-04-08T20:51:42Z")

</div>

thanks, @huey. do you have an ETA for the next update?

---

<div class="post-metadata">

**Author:** ![huey](https://bisq.community/letter_avatar/huey/32/6_22734026db12803ebb3e059622ac3534.png) [@huey](https://bisq.community/u/huey)\
**Post date:** [April 8, 2020, 8:52pm UTC](https://bisq.community/t/error-message-for-new-trade-in-1-3/9245/4 "2020-04-08T20:52:51Z")

</div>

Any time now.

---

<div class="post-metadata">

**Author:** ![huey](https://bisq.community/letter_avatar/huey/32/6_22734026db12803ebb3e059622ac3534.png) [@huey](https://bisq.community/u/huey)\
**Post date:** [April 8, 2020, 9:15pm UTC](https://bisq.community/t/error-message-for-new-trade-in-1-3/9245/5 "2020-04-08T21:15:53Z")

</div>

@decentralizedArtist here it is

> [@Bisq v1.3.1 released](https://bisq.community/t/bisq-v1-3-1-released/9247):
>
> This is a hotfix that improves delayed deposit transaction verification and fixes a bug that marks valid trades as failed trades. [Fix issue with connected transaction output](https://github.com/bisq-network/bisq/pull/4143) Here are the release notes from v1.3.0: Release notes This release is, once again, packed with bug fixes and improvements. Most notably, it reduces the intervals in which users can trigger a trade process refresh. UI [Improve wording for local BTC node reminder in Settings \> Network info](https://github.com/bisq-network/bisq/pull/4024)[Display 2 decimal places for fia…](https://github.com/bisq-network/bisq/pull/3973)

---

<div class="post-metadata">

**Author:** ![decentralizedArtist](https://bisq.community/letter_avatar/decentralizedartist/32/6_22734026db12803ebb3e059622ac3534.png) [@decentralizedArtist](https://bisq.community/u/decentralizedArtist)\
**Post date:** [April 8, 2020, 9:43pm UTC](https://bisq.community/t/error-message-for-new-trade-in-1-3/9245/6 "2020-04-08T21:43:34Z")

</div>

thanks! signature verified, installing now!