# Status of offer always gets disabled after short time

**URL:** <https://bisq.community/t/status-of-offer-always-gets-disabled-after-short-time/11825>\
**Category:** Uncategorized\
**Created:** [January 1, 2023, 7:34pm UTC](https://bisq.community/t/status-of-offer-always-gets-disabled-after-short-time/11825 "2023-01-01T19:34:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Carsen](https://bisq.community/letter_avatar/carsen/32/5_5575768a8748004e209b776fc1b2916d.png) [@Carsen](https://bisq.community/u/Carsen)\
**Post date:** [January 1, 2023, 7:34pm UTC](https://bisq.community/t/status-of-offer-always-gets-disabled-after-short-time/11825/1 "2023-01-01T19:34:10Z")

</div>

I created a new offer to buy BTC. The offer always disappears from the list of trades, on the the list of open offers it then appears as disabled.  
Changing the status back to enabled, or changing the price, or rebooting the client… nothing helps, the status always changes to be disabled after some time.  
My client version is 1.9.8. The maker fee transaction is confirmed. The only maybe unusual fact is that I have another open trade (I wait for the BTC sellers confirmation) - but I think that should’nt be a problem?.

---

<div class="post-metadata">

**Author:** ![Dino](https://bisq.community/letter_avatar/dino/32/5_5575768a8748004e209b776fc1b2916d.png) [@Dino](https://bisq.community/u/Dino)\
**Post date:** [January 2, 2023, 12:14am UTC](https://bisq.community/t/status-of-offer-always-gets-disabled-after-short-time/11825/2 "2023-01-02T00:14:15Z")

</div>

+1  
I am encountering the same issue currently where offer is removed from the market after a short time and appears disabled. I don’t have a current trade open.

Info:  
Client v 1.9.8  
Using custom node  
Using Tor for Bitcoin network  
Maker fee transaction confirmed

Troubleshooting attempts:  
Made new transaction  
Rebooted client  
Deleted and re-synced SPV chain  
Deleted outdated tor files  
Re-downloaded v1.9.8

All unsuccessful at resolving issue.

---

<div class="post-metadata">

**Author:** ![Carsen](https://bisq.community/letter_avatar/carsen/32/5_5575768a8748004e209b776fc1b2916d.png) [@Carsen](https://bisq.community/u/Carsen)\
**Post date:** [January 2, 2023, 10:30am UTC](https://bisq.community/t/status-of-offer-always-gets-disabled-after-short-time/11825/3 "2023-01-02T10:30:29Z")

</div>

Seems to have been a network related problem… Today I started the client, set the offer to active and now the (same) offer works as usual.  
Can anyone explain what the problem was?

---

<div class="post-metadata">

**Author:** ![Pazza](https://bisq.community/user_avatar/bisq.community/pazza/32/2703_2.png) [@Pazza](https://bisq.community/u/Pazza)\
**Post date:** [January 3, 2023, 3:32pm UTC](https://bisq.community/t/status-of-offer-always-gets-disabled-after-short-time/11825/4 "2023-01-03T15:32:25Z")

</div>

@Carsen and @Dino

There is currently an issue where offers with BSQ used for the trade fees might end up being disabled. There is a pull request to fix this that will be included in the next release: [Validate BSQ fee payment using DAO tx info. by jmacxx · Pull Request #6425 · bisq-network/bisq · GitHub](https://github.com/bisq-network/bisq/pull/6425)

The bug does not affect all offers, just the ones paid with BSQ and even then only some of the time. For current offers affect you can leave them and activate them next release to avoid wasting your trade and mining fees.

---

<div class="post-metadata">

**Author:** ![Carsen](https://bisq.community/letter_avatar/carsen/32/5_5575768a8748004e209b776fc1b2916d.png) [@Carsen](https://bisq.community/u/Carsen)\
**Post date:** [January 4, 2023, 3:44pm UTC](https://bisq.community/t/status-of-offer-always-gets-disabled-after-short-time/11825/5 "2023-01-04T15:44:26Z")

</div>

In my case the offer was not paid with BSQ.  
Anyway the problem does not occur any longer.