Introduction to replay executions

Preview — Replay executions

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of theService Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see thelaunch stage descriptions.

With Application Integration you can replay executions by rerunning the original integration as a new integration execution. Application Integration flows are designed to orchestrate communication and data exchange between different systems. These flows can be complex, involving multiple steps, and often rely on interactions with external third-party systems. As a result, your executions can sometimes fail due to various reasons including the following:

  • Errors within the flow: Your integration flow contains incorrect logic such as faulty data transformations or misconfigured steps.
  • Issues with external systems: Problems or downtime with third-party systems–such as databases, web services, or APIs–that the integration flow interacts with.
  • Transient network errors: Temporary glitches in connectivity between systems involved in the integration.

After debugging failures in your published integrations, you canreplay your integration executions. Replaying an execution regenerates the flow and reprocesses the original integration as a new integration execution.

Note: Replaying an execution is only available for published integrations. You cannot replay an execution for unpublished integrations.

Benefits

Replaying an execution can be useful for the following scenarios:

  • Trigger event handling: When you want to rerun a failed execution, especially one triggered by an external system, replay allows you to configure the input variables that would have been provided by that event. For example, suppose that you have an integration with a Pub/Sub trigger that is triggered on receiving an event from an external application such as Jira. When you replay the execution, the trigger event from Pub/Sub is executed as it might be difficult to trigger the same event from Jira.
  • Retrying failed executions: If your integration fails due to transient errors or issues with external systems, you can replay the execution to re-run the flow and complete the integration.
  • Validating published integrations with modified input values: Replay allows you to test published integrations by re-running them with different input variable values. This saves time by avoiding the need to manually rerun the entire integration. Both masked and unmasked variables can be modified during replay.
  • Replaying executions from point of failure: Replay allows you to rerun executions from the point of failure in a published integration. This avoids unnecessary re-execution of successful tasks, saving debugging time and resources.

To learn more about how to replay executions, seeReplay executions.

Considerations

The following considerations apply to replay executions:

Limitations

Replaying an execution is subject to the following limitations:

  • Replaying an execution that is triggered by aSchedule trigger isn't supported.
  • By default, replayed executions have a deadline time of 10 minutes. If the execution does not complete within the deadline, the execution status is set toCANCELLED.

What's next

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.