Hi,
I would suggest first check the program log for any obvious messages.
MarkV, i am using it at the moment with no active trigger and the only thing that appears are the trigger being logged on the opening of MFPro, goals being scored and
markets settled. So, i guess that´s not the way.
The behaviour you are describing sounds like markets or events being placed into the waiting queue according to the limit for simultaneously refreshing markets or events. Check your setting on this in monitoring options settings.
Unfortunatly it seems that the problem isn´t the maximum allowed number of simultaneous refreshing markets/events. I have it with 50 events (see MFPro2).
I agree with you it seems it´s something in the settings that is causing the issue. But i guess that´s not it.
Open the info window of any market and check for any red messages (see the attached screenshot).
Oxa, i did the way you asked and there was nothing at red (see MFPro5).
Later on, the market as you can see in MFPro5 i was refreshing 162 markets (i know it´s too much, but this it´s just to solve this issue and the refresh rate in-play is just 40s), and 161 out of the 162 were idle. After a while, most of these markets changed to inplay. Again, they were supposed to be always in-play.
On the afternoon, i was monitorizing only 4 events, and, even so, 3 out of 4 events had all markets at a certain moment suspended (see MFPro1). It started with only 2 markets of one of the events, and after about 15 minutes, it expanded to the other markets of that same event and to the other 2 events. After a while the process was reversed and most of them appeared inplay again (see MFPro3 and MFPro4) .
Thanks to both