Is there any way to limit an OBLPN from being shipped before the task it belongs to is complete?

Summary:

We have experienced clients during UAT shipping out Oblpns prior to completing its task zone move rules in which the task is in status "In Drop/Between Zones", and was wondering if there was a way to ensure the task has been completed prior to shipping, instead of having the opportunity to skip steps in the end-to-end process.

Content (please ensure you mask any confidential information):

Currently the only way to address this issue is through continuous user training rather than any configurations.

Version (include the version you are using, if applicable):

25A.03m

Code Snippet (add any code snippets that support your topic, if applicable):