We had Lazy Approval on and working perfectly for some time. Recently we decided to stop the Microsoft SharePoint Foundation Web Application service on our APP server as it isn't serving as a WFE. We have other 3rd party solutions that are basing their licensing cost on "WFE" (AKA: any server that is running the Foundation Web Application service, regardless of its actual role) thus costing them extra for licensing fees.
After making this change, the Lazy Approvals stopped working. The workflow would start as expected, but the Lazy approval would show as a failure (regardless of the response) and ultimately the entire workflow fails.
After a few days of troubleshooting, we started this service back up and the approvals started working normally.
My question is: Why does this impact the Lazy Approval process, and is there any way of circumventing it?