Currently, when a user clicks Publish / Go Live on a Real-Time Marketing Journey, the action bypasses the standard Dataverse plugin pipeline. This means InvalidPluginExecutionException thrown in a plugin does not surface as a user-facing error on the Journey form.

Request: Expose the Journey Publish action through the standard plugin pipeline so that custom business logic (approvals, validations, compliance checks) can block publishing and show meaningful error messages to users just like any other Dataverse entity.

Business Impact: Organizations need approval gates before Journeys go live to prevent unapproved marketing communications going to customers.