---
schema_version: "1"
id: 9ae301518754b4060b5bd7ad664a4ac2781660f6ed5a15e5ed3cf66dbf188eb4
title: Long-Running Integration Procedures
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_long_running_integration_procedures_56206.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_long_running_integration_procedures_56206.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 979715a9c73d89543f2d9e85ed3bfc7c0de6d6d1d206f230e7e70c1b4660715a
description: When invoking long-running Integration Procedures you can avoid hitting Salesforce governor limits by using chainable and queueable chainable settings or Apex Continuations, or by chaining on one or more specific long-running steps.
products:
  - Omnistudio
release: "264"
---
# Long-Running Integration Procedures

When invoking long-running Integration Procedures you can avoid hitting Salesforce governor limits by using chainable and queueable chainable settings or Apex Continuations, or by chaining on one or more specific long-running steps.

- **[Settings for Long-Running Integration Procedures](https://help.salesforce.com/s/articleView?id=xcloud.os_settings_for_long_running_integration_procedures_56206.htm&release=264.0.0&type=5)**  
    You can use chainable and queueable chainable settings to avoid hitting Salesforce governor limits when invoking long-running Integration Procedures. You can also chain on one or more specific long-running steps.
- **[Continuation in Long-Running Calls](https://help.salesforce.com/s/articleView?id=xcloud.os_continuation_in_long_running_calls_56418.htm&release=264.0.0&type=5)**  
    To support long-running calls, Salesforce provides Apex Continuations. If your Omniscript calls a long-running Integration Procedure or Apex class, you can enable continuation. If your Flexcard calls a long-running Integration Procedure that has an HTTP action or a Remote Action, you can enable continuation.