Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Integration Incompatibility Feature

edited Apr 10, 2023 5:51PM in Idea Lab – Integration Cloud 4 comments

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

Tagged:
11
Up Down
11 votes

Submitted · Last Updated

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!