See the supported connectors for Application Integration.

Timer task

The Timer task lets you add a time delay to the integration execution flow.

During an integration execution, when the control reaches the Timer task, execution is paused for the specified time limit, and all tasks after the Timer task are suspended. The integration resumes the execution after the time limit expires.

Configure the Timer task

To configure the Timer task:

  1. In the Google Cloud console, go to the Application Integration page.

    Go to Application Integration

  2. In the navigation menu, click Integrations.

    The Integrations page appears listing all the integrations available in the Google Cloud project.

  3. Select an existing integration or click Create integration to create a new one.

    If you are creating a new integration:

    1. Enter a name and description in the Create Integration pane.
    2. Select a region for the integration.
    3. Click Create.

    This opens the integration in the integration designer.

  4. In the integration designer navigation bar, click Tasks to view the list of available tasks.
  5. Click and place the Timer task element in the integration designer.
  6. Click the Timer task element on the designer to view the Timer task configuration pane.
  7. Configure the remaining fields using the Configuration properties for the task as detailed in the tables below.
  8. Changes to the properties are saved automatically.

Configuration properties

The following table describes the configuration properties of the Timer task.

Property Data type Description
Timeout after Integer

Time till which the integration execution must be paused. Integration automatically resumes the execution of the next downstream task after the expiry of the time limit.

Default value: 120 seconds (2 minutes).

Maximum time limit allowed: 44640 minutes (31 days).
Time unit NA Time unit for the Timeout after property.

Compare Approval task, Suspend task, and Timer task

All the three (Approval, Suspend, and Timer) tasks perform a similar function of pausing and resuming an integration. However, there are subtle differences among them. The following table describes the differences amongst the three tasks.

Approval task Suspend task Timer task
Doesn't support automatic resumption of an integration and requires manual intervention to resume the integration. Supports both manual and automatic resumption of an integration. If there is no manual intervention to revoke the suspension, the integration will automatically resume execution after the expiry of the suspension time limit. Supports only automatic resumption of an integration. The integration execution automatically resumes after the exipry of the suspension time limit.
Can't resume an integration via an API call. You must manually resolve the suspension by using the Integrations UI. Can resume an integration by using the Suspensions API for integrations. Supports only automatic resumption of an integration.
Users receive notification when an integration pauses (suspended). Users don't receive any notification when an integration pauses (suspended). Users don't receive any notification when an integration pauses (suspended).
Supports a output variable (boolean), which allows you to perform conditional checks before resuming an integration. However, the output variable can only have the value as either true or false. Supports a output variable (string), which allows you to perform conditional checks before resuming an integration. You can set any value to the output variable. Doesn't support any output variables.

Error handling strategy

An error handling strategy for a task specifies the action to take if the task fails due to a temporary error. For information about how to use an error handling strategy, and to know about the different types of error handling strategies, see Error handling strategies.