When using load balancing or clustering, it is important that requests do not rely on modifications made by previous requests. For example, a request could run a script that modifies a set command option. The set command option will be modified only on the Arbortext PE sub-process running on the Arbortext PE server handling the request. A request to Arbortext Publishing Engine can't rely on any action performed by a previous request. Requests are fulfilled by multiple Arbortext PE sub-processes that do not maintain a session state or record of a previous reques. Subsequent requests could go to a different Arbortext PE sub-process or a different Arbortext PE server. This means that Arbortext PE Request Manager has no information to determine how to route subsequent requests based on previous ones.