No. However, we found out that they had a system outage last week. This is what the WF error log has:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

The bizarre part is that all Laserfiche services seemingly recovered from this once SQL Server came back up, except WF Subscriber. It was in a started state, but not doing anything, and had to be restarted manually. WF business processes could still be triggered from the Client, and Forms could also trigger them - just the ones started by repository events weren't working.

Does your time on the server that houses workflow get changed or sync'd?  We discovered that our workflow server was stopping randomly as well.  Tracked it down to when the system time got sync'd and went backwards a few milliseconds while a workflow was running, it stopped running.  Restarting the service always fixed it.  We stopped the program that was syncing the time and have not had that problem since.