Lotus Workflow is not build to work within a clustered environment. The engine relies on an agent written in LotusScript, which is scheduled like any other agent. If this agent will run on different servers on the same documents this will cause numbers of save-conflicts. If it is tied to just one machine, the cluster is virtual worthless, because of the manual switchover in case of failure of that server.
Another component suffering in a clustered environment is the web-viewer: It is implemented as a servlet running on a the Domino server. I cannot tell why, but it does not work properly in clustered environments. The user will not receive the desired diagram, but will be presented an error message.
Some of this problems may be addressed. For example you may split your workflow application into smaller applications hosting just a single workflow. This gives you the chance to schedule different backgrounders to different machines. But, to be honest, this is not the sort of thing you want to do, when thinking about clusters. You just want your big application to work as if there was no cluster at all!
The web-viewer could be cheated by using a fixed server, f.e. by using a proxy and redirect calls to a single machine – Again a solution which is not just positive: What about a failure of the server hosting the web viewer?
I posted an idea on the LWF-IdeaSpace recently, which proposes to make Lotus Workflow aware of clusters. If you think that is a problem, please promote my idea.
Maybe you found other solutions to overcome the hassels of a clustered environment? Just let me know!