OIC - OIC Scheduled Integrations: Does Ad-Hoc Run Impact Scheduled Run Parameters?

When working with Scheduled Integrations in Oracle Integration Cloud (OIC), a common doubt is:

If I run the integration manually (Ad-Hoc / Run Now), will it impact the scheduled StartTime / EndTime values?

✅ Correct Answer (Based on Testing)

No — Ad-Hoc run does NOT impact scheduled parameter values.

There is no direct relationship between Ad-Hoc execution and Scheduled execution parameter persistence.

📌 How It Actually Works

1️⃣ Scheduled Run

Triggered automatically by OIC Scheduler

Uses stored schedule parameter values

Follows recurrence (15 min / hourly / daily etc.)

Parameter continuity works only within scheduled executions

2️⃣ Ad-Hoc Run (Run Now)

Triggered manually from OIC Console

You may override parameters at runtime

Executes independently of scheduler

Does NOT modify schedule configuration

Any values entered during Ad-Hoc run are used only for that execution.

🔍 Important Clarification

Earlier confusion usually comes from watermark/rotation logic like:

StartTime = EndTime

EndTime = sysdate

If your integration updates values internally, that affects the current run execution only.

It does NOT update the scheduler’s stored parameters.

The next scheduled run will still use the originally configured schedule parameters.

📊 Final Behavior Summary

Scenario | Impacts Next Scheduled Run?

Ad-Hoc run (no changes) | ❌ No

Ad-Hoc run (override values) | ❌ No

Scheduled run | ✅ Uses its own stored schedule values

Internal variable assignment for adhoc run ,| ❌ Does not change scheduler config

🎯 Final Conclusion

✔ Ad-Hoc run is completely independent

✔ It does NOT update scheduler stored parameters

✔ Scheduled runs continue with configured values

✔ No cross-impact between Ad-Hoc and Scheduled runs