Hi
Are you now running 2x Profiles each with much lower Data Request limits?
Either way, if the number of refreshing markets and related data requests such as bets update, score, statement, silks etc. cannot be serviced within the Request Limit for the Profile, a backlog of requests will build up, and this will get compounded. When this occurs, the program becomes very slow to respond, and has a higher risk of crashing.
I suggest you test a small number of refreshing markets first. When you are confident everything is running well, then slowly add more markets and test further. Keep doing this until you find the point where the software starts to become slow to respond.
If the above is true, you will either need to reduce your number of monitored markets and / or their refresh rate, or increase the Data Request limit and incur the charge.
Another possibility is your trigger file may be generating the problem, perhaps with a logic loop or something similar. My suggestion here would be the reverse of above: load in your usual number of markets, but use a known working trigger file such as one of the example triggers. Run it and test. If that works OK, then the problem must be in your trigger file.
