when an integration is deactivated and then reactivated
Summary:
In Oracle Integration Cloud (OIC) Gen3, when an integration is deactivated and then reactivated, we observe in the Observability Instances tab that all previous runs are marked as aborted, even though those runs were not actually executed on the dates shown.
For example, consider integration_A, which is scheduled to run daily every hour. In the Observability Instances tab, we can typically see all the successfully completed runs. However, if we deactivate and then reactivate the integration due to deployment or maintenance, we notice something unusual after reactivation. When checking the Observability Instances tab, we see earlier dates showing aborted integrations (those runs were not captured on earlier dates). The integration appears to have been running on an earlier date but was aborted at today's deactivation time and date.