activities
latest
false
UiPath logo, featuring letters U and I in white

Integration Service Activities

Last updated Jan 28, 2025

Long-running workflows with Integration Service activities

Integration Service provides support for long-running workflows with dedicated activities. All Integration Service connectors include a Wait for an Event on {Connector} and Resume activity. Its purpose is to suspend a job at runtime and resume the job whenever a certain event occurs in a third-party application.

Wait for an Event activities in Studio Web
Wait for an Event on Salesforce and Resume
Note:
Wait for an Event and Resume is available for all connector activities delivered through the unified UiPath.IntegrationService.Activities package.

In Studio Desktop, Wait for an Event and Resume it is listed in the Activities panel, in the Available section, for each connector. In Studio Web, you can find it using the activity browser. For details, see Working with Integration Service activities.

Why use long-running workflows


Long-running workflow diagram

Suspending workflows can bring multiple individual workflows together into one. It helps address human-in-the-loop scenarios or events from outside of the workflow, maintaining the state and scope of the full workflow at resume time. This makes the general workflow overview and jobs easier, and keeps the context of the full object or dataset the workflow is processing. The context of the job lives on, until its dataset reaches a certain status.

Suspending workflows also removes separate filtering you may have to perform in individual workflows. If you are interested in certain updates to a specific record, you can perform filtering on a specific record as part of the activity, rather than trigger multiple jobs.

How long-running workflows work

The Integration Service support for long-running workflows is based on the Integration Service triggers framework and the existing Persistence activities.

Every Integration Service connector that supports events also supports long-running workflow capabilities on the same events. For example, the Salesforce connector supports the following events: Account Created, Contact Created, Opportunity Created, Lead Created, Opportunity Closed and Won, Record Updated, and Record Created. The same events are available for selection in the Wait for an Event on Salesforce and Resume activity.

At runtime, when a job moves into the Suspended state, it creates a temporary trigger in Integration Service. This trigger disappears once the event occurs in the vendor system. When that happens, Integration Service gives Orchestrator a Resume Job instruction. Orchestrator resumes the existing job, moving it out of the Suspended state back into Running state. The job then continues with the full context and state that it had before being suspended, and with the input of the event activity. When the job is successfully resumed, Orchestrator instructs Integration Service to remove the temporary trigger.

Note:

Temporary triggers are created in Integration Service only at runtime, not at design time. When testing, the process pauses when it reaches the Wait for activity. At that point, you can manually go to the vendor application, perform the required action (approve an order, for example), then select Continue in Studio to resume the execution.

Example

Here is an example workflow with a Wait for an Event and Resume activity.

  1. Trigger a workflow when an order in Salesforce is created, using the Record Created trigger for an Order object.
    Note: The order is identified using its order ID. This ID is used further in the workflow to capture updates in that particular order.
  2. Take a series of steps, such as retrieving customer information and order items.
  3. For the order to be processed further by the workflow, a sales manager needs to step in and perform an action on that order, such as approving it in Salesforce. This is where you use the Wait for an Event on Salesforce and Resume.
  4. When the workflow reaches the Wait for activity, it pauses. The job is temporarily suspended, waiting for an update on an order with a specific identifier (the object ID retrieved at step 1).
    1. In Orchestrator, in the Jobs page, the state for your process changes to Suspended.
    2. In Integration Service, in the Triggers tab, a Record Created temporary trigger is created, waiting for an action to happen in Salesforce.
  5. In Salesforce, the order gets approved.
  6. Polling every five minutes (or according to configuration), the Integration Service trigger identifies the event in Salesforce.
  7. Once the event is identified, the process execution is resumed.
    1. In Orchestrator, in the Jobs tab, the state for the process changes from Suspended to Running.
    2. In Integration Service, the temporary trigger is deleted.
  • Why use long-running workflows
  • How long-running workflows work
  • Example

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo White
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2025 UiPath. All rights reserved.