Only restart of Smart Reporting can get broadcast schedules to run again
We are left perplexed with an issue which we are seeing across several sites whereby only a restart of SR can reinstate broadcast schedules after they all stop running.
So far, the behavior that's been observed is based off the logs where all the background queues(5) get filled, and it seems that the 5 tasks that have been already queued never starts/finish to run (see 15160-09-18 for some context)
For the current scenario, however, it seems broadcast schedules stopped from running after an error in the following error in the log (see smartreporting.log.6 before restart):
ERROR (552): The SQL database operation failed.; The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.
The problem is that we cannot tell which report caused the error from the logs and also don't understand why an error like that would cause broadcast schedules to stop from running.
Is there any explanation/reasoning that you could to explain why all broadcasts stop from running and needing a restart?
I have uploaded the logs via the FTP site for your review, before and after restart.