Guardian going to sleep

[noseve]

Evening all - until recently I have happily run three instances of BA simultaneously, quite happily, on this laptop, each one loaded with identical markets, logging to its own log folder. There would often be 800 or more markets listed, each linked to 5 rules.
As a result of playing with ways to capture the event id, I fell upon a regime of having PHP query the API to carry out various tasks such as store the eventId in a stored value, apply a coupon to fetch certain markets in a certain timeframe, apply rules, then delete the older markets using a safe enough threshold to allow some post-market close routines to run. I had not used a coupon before, but it seemed very similar to applying market filters, with which I am familiar and which I used to apply with a keyboard shortcut. Working with a market filter I never had a problem, even though the market list was invariably larger - in each of three instances - than I ever have loaded now, in just a single BA instance.
After a variable period, maybe 12 hours, or 24 hours or occasionally more, I find that Guardian has effectively gone to sleep. The only logged action is the pre-off eventId sv generated by the API call above. These are all football markets, and I can even be watching an affected match, so I know that they haven't all be postponed. My csv exports, which are automatically added to a MySQL database, all reach the end of their logging for any market that they began, but after failure point no new events are even acknowledged, save repeated entries for the API-generated eventId. These are the result of a Windows scheduled task running the API calls every 15 minutes. This has a typical runtime of 5-12 seconds and never coincides with any other scheduled tasks. (EDIT: I originally quoted runtime for a different task)
The market additions and deletions continue to work perfectly, in accordance with the thresholds set. All rules are applied accurately. There is nothing different about anything that is either performed or happens before the fail.
Sometimes it is falling asleep with no more than 300 markets in. I am not restricting the refresh, and have experimented with Guardian refresh interval, which has been set on 20ms since I can remember, but this seems to make no difference.
Any ideas? BA's workload must be a fraction of what it used to be. The detailed log for the API call lists all numbers which make sense with what I see. All rules are definitely being applied. The only remedy is to shut town BA and restart.
Even stupid suggestions welcome!

[ODPaul82]

From reading this the only item that you seemed to have changed is introduce php and mysql for the event ID which to me would be the bottleneck.
I run multiple instances of BA with guardian being automatically updated and rules applied 24/7
This is all triggered from custom C# programs so all done exclusively via the API.

Is your php code multi-threaded?
Have you operated any debugging to see if there are any bottlenecks with your code?
Are your queries throttling on the result back that your application is waiting on?

[noseve]

Thanks for your reply, appreciated - no, there's no apparent php bottleneck - I can see the log at the same time as the guardian market list is populated and the task only lasts a few seconds.
Once the markets are in the list, with rules applied and with the market log displaying the eventId stored value (as determined by the API call) which presumably confirms that the market has been registered/acknowledged properly by Guardian, That must be the end of the PHP script involvement, mustn't it? The task takes a few seconds to run and its log added/removed counts exactly match the guardian market list tally every time.

The only other new thing, to me, is the coupon, but again, the market list is populated perfectly, so it is difficult to see how that could be causing the issue. I used to have BA running for a few weeks, with no issues and these same rules applied, often with close to a thousand markets, with no problem.

The failure is so clean, though, with all markets currently activated logging all collections right through to event end - there are no orphaned csv files. All very strange. Almost as though the rules are simply being ignored, despite being listed in the usual columns. A puzzler.

Everything else on the computer works fine, even after the problem manifests itself - although temporarily I'm treating this machine as a dedicated Bet Angel laptop.