arnelhbot

Tested on Master-v1.6.0 and Dev1.7.0. This issue is still visible. Master-v1.6.0 ``` 2022-07-26 07:24:39,706 - 1313558 - hummingbot.client.hummingbot_application - ERROR - local variable 'last_subparser' referenced before assignment Traceback (most recent...

Also encountering the same issue when cloning and compiling ``` Traceback (most recent call last): File "/home/ubuntu/miniconda3/envs/hummingbot/lib/python3.8/multiprocessing/pool.py", line 125, in worker result = (True, func(*args, **kwds)) File "/home/ubuntu/miniconda3/envs/hummingbot/lib/python3.8/multiprocessing/pool.py", line 48,...

Issue Update: Currently in Dev 1.6.0 and Master v1.5.0 Dev1.6.0  Master v1.5.0 

Issue Update: Issue showing on dev1.6.0 in where bot has failed to refresh orders, during bot failed to check that order was cancelled on the exchange. Bot flooded with Failed...

Issue Update: Tested on Dev1.7.0 we did not observe any failed order status not found during our testing - Closing PR  [logs_conf_liquidity_mining_1.log](https://github.com/hummingbot/hummingbot/files/9382354/logs_conf_liquidity_mining_1.log)

Hi @KlaSun, thanks for reporting this issue. We were able to replicate your issue. Upon testing `Dev1.8.0` & `Master v1.7.0` with `Perp_MM` using `Binance_perp`, we noticed that there was a...

> Thanks. Are you able to keep trading after the warning ? I lose connectivity and have to stop and restart the script Hi @KlaSun from our testing, yes the...

A possible scenario why this issue has occurred could be with Binance API Keys. There are cases where users don't whitelist their IP address, when they do this they can...

Hi @KlaSun, just to confirm, you are using a personal script and not a strategy, correct?

Hi @KlaSun, @leastchaos & @keithbaum, can you please confirm if this issue for `failed to refresh listen key` has been fixed or if it's still persistent?