Prevent duplicate journey assignment

Summary:

Is there a way to prevent duplicate journeys from assigning to the same person if the template is currently in-flight? Essentially the way Onboarding journeys work but applied to Person journeys.

Content (required):

We are solutioning our Connected Workplace/Return to work program utilizing an attribute on the person's assignment that defaults from their job. During a transfer, a manager is able to request an exception to the job default which then will require the employee to acknowledge a specific policy. However, they only need to sign this acknowledgment one time. We're finding cases where managers are submitting multiple transactions (corrections, teams, etc.) and it's triggering multilple journeys of the same type to be allocated to the employee so one employee may have 2-3 inflight at the same time. We are managing this by