Blank markets in Guardian

[fishtownraider]

Lately I've found that some markets are being left blank in Guardian. It started when I added a third market to my market selection filter, increasing the size of the list by around a third. The blank markets are not being refreshed, which I guess is why they're blank, but the start times column is completed, and when I fire a shortcut that adds one of three rules to the Automation Rules column depending on which market is selected, it adds the rules (correctly, I'm guessing), so Guardian must 'know' what the blank markets are. The picture shows just a few lines for comparison, but there are actually about 200 of them.

Screenshot 2024-06-22 130332.png

[Euler]

These look like matches that had already finished but are still in the Betfair market tree when you last refreshed.

[jamesedwards]

This happens when you load more than 1024 markets into Guardian. If you delete some unused markets the remaining markets will populate.

If you want to trade on more than 1024 markets at a time you need to open more than one instance of Guardian.

[fishtownraider]

This happens when you load more than 1024 markets into Guardian. If you delete some unused markets the remaining markets will populate.

If you want to trade on more than 1024 markets at a time you need to open more than one instance of Guardian.

That's useful to know (if somewhat annoying ). Thanks, James.

[Anbell]

This happens when you load more than 1024 markets into Guardian. If you delete some unused markets the remaining markets will populate.

If you want to trade on more than 1024 markets at a time you need to open more than one instance of Guardian.

Or you can switch off streaming

[fishtownraider]

This happens when you load more than 1024 markets into Guardian. If you delete some unused markets the remaining markets will populate.

If you want to trade on more than 1024 markets at a time you need to open more than one instance of Guardian.

Or you can switch off streaming

Thanks, Anbel. I'm only refreshing Guardian at 200ms anyway, so that won't be a problem.