In several situations, the Mendix client triggers an xas request to the backend even though the operation could be handled entirely client-side:
- retrieval via association between NPEs: In 9.24 this was optimized for the retrieve action in NFs but for association data sources in, e.g., list views the xas request still happens
- commits: Commits on NPEs in NFs always cause an xas request, even if there are no before/after commit event handlers registered for the corresponding entity (and the client already knows for which events handlers are registered through the needsReachableState flags)
- cancel/rollback, same as for commits: Rollbacks (triggered by a cancel button or by the rollback action in a NF) cause an xas request even if there are no persistent entities affected and there are no related event handlers to be considered. Furthermore, also rollbacks on persistent entities could be handled client-side as long as no object creations need to be reverted and no event handlers are involved.