Known Issue for Integrations with Private Endpoint Connectivity: Publish/Consume Messages Failure for Inactive Integrations

If your active integration has not run for more than three days, you may encounter the errors listed below depending on the integration’s configuration:

  • If you set up an invoke connection, you may encounter a Connection Reset error while trying to publish a message.
  • If the integration is configured as a trigger connection, you are unable to consume or read any message.

This is a known issue and has occurred because the connection access type is a private endpoint. This issue has been addressed in the 26.07 release. You do not encounter this issue if your Oracle Integration instance has been upgraded to version 26.07.

If your Oracle Integration instance has not been upgraded to 26.07, this issue occurs. As a temporary workaround, reactivate the integration to resolve the issue until you can upgrade.

Note:

You only need to reactivate the integration once. Next time, if your integration goes idle for more than three days, this issue does not occur.

Follow these steps in Oracle Integration to reactive the integration:

  1. Log in to your Oracle Integration instance.
  2. Navigate to Design, then Integrations.
  3. Browse for your integration in the list.
  4. If the integration is in the Active state, click Deactivate.
    The integration moves to the Configured state.
  5. Click Activate to reactivate the integration.