I had a 5 minute polling strategy running in the Strategy Monitor, using the Binance broker extension. It was running fine for a couple days, but then when I checked it tonight it had somehow changed to "deactivated". These are the last lines in the log:
If there was some temporary network outage that caused the historical request to time out, is it the intended behavior that the strategy deactivates?
QUOTE:
2/24/2023 19:10:05: Processed all Symbols
2/24/2023 19:15:01: Status = Processing
2/24/2023 19:15:01: Pass 1 - Requesting updates for 97 symbols...
2/24/2023 19:15:05: Pass 1 - UpdateHistories returned 97 symbols
2/24/2023 19:15:06: Ran Strategy on KDAUSDT,LRCUSDT,ENSUSDT,GRTUSDT,YFIUSDT,CRVUSDT,ASTRUSDT,ETHUSDT,JAMUSDT,1INCHUSDT,AUDIOUSDT,BANDUSDT,NEARUSDT,KNCUSDT,ACHUSDT,AXSUSDT,SHIBUSDT,PAXGUSDT,CTSIUSDT,ENJUSDT,MANAUSDT,ONEUSDT,AAVEUSDT,ADAUSDT,ETCUSDT,BCHUSDT,UNIUSDT,DGBUSDT,LTOUSDT,BNBUSDT,WAXPUSDT,ALICEUSDT,LDOUSDT,BTCUSDT,MATICUSDT,JASMYUSDT,KSMUSDT,SANDUSDT,CELRUSDT,FTMUSDT,ZENUSDT,ALPINEUSDT,SLPUSDT,SPELLUSDT,ONTUSDT,RNDRUSDT,BATUSDT,SNXUSDT,TLMUSDT,RENUSDT,RLCUSDT,FETUSDT,STORJUSDT,QTUMUSDT,ALGOUSDT,BICOUSDT,FILUSDT,HNTUSDT,DOGEUSDT,ROSEUSDT,MASKUSDT,FLUXUSDT,NEOUSDT,COMPUSDT,APEUSDT,TFUELUSDT,ATOMUSDT,FORTHUSDT,VETUSDT,VITEUSDT,LINKUSDT,SOLUSDT,GALUSDT,AVAXUSDT,THETAUSDT,XLMUSDT,NMRUSDT,DOTUSDT,STGUSDT,IMXUSDT,GALAUSDT,API3USDT,COTIUSDT,MKRUSDT,TRXUSDT,LOKAUSDT,OCEANUSDT,ICPUSDT,EGLDUSDT,OXTUSDT,KAVAUSDT,APTUSDT,TUSDT,OPUSDT,LTCUSDT,VTHOUSDT,RAREUSDT: 0 Signals, Run Time=423ms
2/24/2023 19:15:06: NextRun set to 2/24/2023 19:20
2/24/2023 19:15:06: Status = Completed
2/24/2023 19:15:06: Processed all Symbols
2/24/2023 19:20:00: Status = Processing
2/24/2023 19:20:00: Pass 1 - Requesting updates for 97 symbols...
2/24/2023 19:20:32: Exception: One or more errors occurred. (Binance Historical Request Error (LRCUSDT): [55248] Request timed out)
2/24/2023 19:20:32: Status = Deactivated
2/24/2023 19:20:32: Leaving Polling Thread
If there was some temporary network outage that caused the historical request to time out, is it the intended behavior that the strategy deactivates?
Rename
It is the intended behavior that the Strategy has deactivated on an exception during a streaming/polling data collection run.
That may be true, but it probably shouldn't happen due to the first request timeout - and for only one of dozens of symbols. Let's improve that.
Thank you, a change to the behavior would be greatly appreciated. The strategy monitor had opened a position shortly before it deactivated, so unfortunately the strategy did not exit the position when it otherwise would have.
This is in place for Binance Build 19.
But you shouldn't be using Binance polling for 5 minute bars. There will be a lot of delay and even more when many instruments like these don't have any trading.
Binance has Streaming Bars that work instantaneously. However, I discovered that they're not respecting the "Load Zero Volume Bars" option in the the Binance configuration. This is also fixed for Build 19. (If you like loading zero volume bars, then everything works great right now).
But you shouldn't be using Binance polling for 5 minute bars. There will be a lot of delay and even more when many instruments like these don't have any trading.
Binance has Streaming Bars that work instantaneously. However, I discovered that they're not respecting the "Load Zero Volume Bars" option in the the Binance configuration. This is also fixed for Build 19. (If you like loading zero volume bars, then everything works great right now).
But there is another trouble.
Strategy is being deactivated by itself suddenly after running.
HEre is log screen
in Log viewer all is ok
Strategy is being deactivated by itself suddenly after running.
HEre is log screen
in Log viewer all is ok
Now in log view appeared this message below
Please wait until Binance Build 19 is released.
The log indicates "Running Now" which means you clicked the Run Now option. So yes it is expected for the Strategy to then deactivate after it runs.
If you'd like to keep the Strategy active after selecting Run Now, turn on this preference:
If you'd like to keep the Strategy active after selecting Run Now, turn on this preference:
QUOTE:
Please wait until Binance Build 19 is released.
It has been released ,, but the error is alive still ((
I released Binance Build 20 that uses the latest CryptoExchange.NET package. It also writes out the listen key to the WL8 log so we can see exactly what's in it.
There was some findings from the CryptoExchange Discord server that indicated that these errors sometimes occur when different language packs are installed and used in Windows, but really no concrete solutions were provided there.
There was some findings from the CryptoExchange Discord server that indicated that these errors sometimes occur when different language packs are installed and used in Windows, but really no concrete solutions were provided there.
Your Response
Post
Edit Post
Login is required