Replay Integration Instances

You can replay REST Adapter-triggered and AS2 Adapter-triggered integration instances that you configured as replayable during integration activation. This feature enables you to quickly retest your integration without the need to re-enter the data used to initially trigger the integration.

• Capabilities and Restrictions
• Understand the Differences Between Replaying and Recovering Instances
• Replay an Integration Instance

Capabilities and Restrictions

• You can only replay instances in which you explicitly select Allow to run again in the Activate integration panel.
• You can only replay instances in which the trigger adapter connection is a REST Adapter or AS2 Adapter.
• You can only replay instances with structured payload content. You cannot replay instances with unstructured payload content.
• You can replay instances regardless of their state (for example, you can replay successful, faulted, and aborted instances).
• You can replay instances outside and inside of projects.
• You cannot replay instances where the connectivity agent is used.
• You can only replay a single instance at a time.
• There must be an active integration with the same major version as the replayed instance.
• A parent instance can have many child-replayed instances.
• A replayed instance has a single parent instance.
• You can replay both asynchronous and synchronous instances.
• Payload data for replayed instances is captured for 32 days (for the Production and Audit tracing levels).

Understand the Differences Between Replaying and Recovering Instances

Instance replay and instance recovery (performed with the Resubmit option on the Errors page) are not the same. Understand the differences to determine which feature is best for your scenario. Instance recovery includes the following restrictions.

• You can only recover a faulted instance that is identified as recoverable.
• You cannot recover synchronous instances.
• You cannot recover scheduled integration instances with scheduled parameters.
• Recovery only updates the existing instance. No new instance is created.
• Recovery is independent of adapter type or payload content.
• Recovery only restarts from the last dehydration point in an instance (for example, a wait action), whereas replay starts completely from the beginning of the instance.

Replay an Integration Instance

This section describes how to replay an integration instance on the Instances page outside of a project. You can also replay an integration instance inside a project. See Activate or Deactivate an Integration in a Project and Track Instances in a Project.

1. In the navigation pane, click Design, then Integrations.
2. Hover over the integration to activate, then click Activate .
3. Select the level of tracing appropriate to your integration. This level describes the amount of data to capture in the activity stream. See Activate an Integration.
4. In the Configure runtime options section, select Allow to run again, then click Activate. This selection enables you to replay an instance of an integration during runtime on the Instances page. This selection is only available with specific types of integrations. See Capabilities and Restrictions.
5. Run the integration. For REST Adapter trigger connection-based integrations, you can use the Configure and run page. See Test Integrations from Outside the Integration Canvas.

   The Activity Stream panel opens.

6. Go to the Instances page in either of two ways:
   1. On the Configure and run page, close the activity stream and click Track instances.
   2. In the navigation pane, click Observability, then Instances.
7. Hover over the row of the instance to replay, and click Run again .

   The Run again panel opens.

8. Select the tracing level to use for this instance replay. The level you select is unique to this replay only and does not impact the tracing level you set when activating the integration.
9. Click Run again.

   When you replay an instance, a new instance ID is created and an icon is added to identify this as a replayed instance. For this example, the replayed instance and the original instance immediately below are shown. You can continue to replay the original instance or the replayed instance.

   
   
   

   Note:

   The Display instances option of the Filter enables you to filter on replayed or replayable instances.
10. Click View details to view the activity stream.
11. Click Actions and note the selections for both the original and replayed instances.
    • The original instance lets you view the replayed child instance.
    • The replayed instance lets you view the replayed parent instance and the replayed child instances.

    You can replay the original instance again or replay the previously-replayed instance again.

    If you no longer want the integration to be replayable, you can change the configuration.

12. In the navigation pane, click Design, then Integrations.
13. Hover over the row of the integration to configure, and select Actions , then Configure activation.
14. In the Configure runtime options section, deselect Allow to run again, then click Save. You do not need to deactivate the integration. The change is applied to the active integration.
15. Run your integration again and go to the Instances page to review the results.
16. Hover over the row for that instance and note that there is no Run again icon for replaying this specific instance.

    Note:

    The instances that you created previously when the integration was replayable still show the Run again icon. However, if you attempt to replay these instances, you receive an error. This is because the integration is no longer replayable.

You can also reprocess (replay) B2B for Oracle Integration instances. See B2B Tracking in Using B2B for Oracle Integration 3.