You can use the ON QUIT statement within a remote procedure to intercept any QUIT condition raised during execution and handle it as your application requires. Otherwise, the QUIT condition propagates to the client application. For information on unhandled QUIT conditions, see Effects of unhandled conditions.

A QUIT condition raised in an Activate procedure for a session running a session-free or unbound session-managed request has the same effect as if it were raised in the remote procedure for the request.

Log file growth due to QUIT in disconnect procedure

When using a QUIT statement in a disconnect procedure to simulate state-reset behavior (as in classic AppServer), PAS for OpenEdge logs the following warning message:
<procedure name> <procedure type> procedure ended with a QUIT condition. (8027)

This is expected behavior. However, in versions prior to 12.2.18, this message is logged every time the disconnect procedure is called, which leads to excessive log file growth. Upgrade to OpenEdge 12.2.18 or later to suppress this warning.