Integration Incompatibility Feature

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

Southern Company

Description (Required):

We have experienced issues with Integrations being scheduled, but then users running the same integration ad-hoc, and then two instances of the Integration will be running simultaneously. Ideally, it should behave like incompatible jobs back in Oracle-EBS, where you could select a job to be incompatible with itself, in this case, we should be able to select an Integration to be incompatible with itself, that way, only one instance can be running at any given time, and instances of the integration would queue and run only after the active one has concluded, if this flag were to be set