---
schema_version: "1"
id: e8171b0f7ec8e32e26e3cd7cb45bb9b4d4f655f450d966ec27fbd9c5af75129f
title: Run Multiple Actions in an Action Block
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_action_block_14046.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_action_block_14046.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5dc71b47a9122584d46ce68621bbb1b2290115c92afef0141e2eaf0887d40c06
description: Run multiple Omniscript Actions asynchronously by grouping them in an Action Block. Actions within the Action Block run in parallel and inherit the Action Block's settings.
products:
  - Omnistudio
release: "264"
---
# Run Multiple Actions in an Action Block

Run multiple Omniscript Actions asynchronously by grouping them in an Action Block. Actions within the Action Block run in parallel and inherit the Action Block's settings.

View the Action Block flow chart to understand how actions in the Action Block execute.

Action Block flow chart:

![image](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/omnistudio/images/action_block_flow.png)

1. From the elements panel, drag the **Action Block** element to the canvas.
    
    Place the Action Block inside a step, before the first step, or between steps.
2. Drag up to four action elements into the Action Block.
3. Select an **Invoke Mode** to control how actions inside the Action Block run.
    
    |  |  |
    | --- | --- |
    | Default | The Action blocks the UI with a loading spinner. |
    | Non-Blocking | The Action runs asynchronously, and the response applies to the UI. Pre and Post Omnistudio Data Mapper transforms, and large attachments aren’t supported. |
    | Fire and Forget | The Action runs asynchronously with no callback to the UI. Pre and Post Data Mapper transforms, and large attachments aren’t supported. A response still appears in the debug console but doesn’t apply to the Data JSON. |
    
    When Invoke Mode is set to non-blocking, elements using default values don't receive the response because the element loads before the response returns. You must configure these properties to map the response to an element:
    
    - **Response JSON Node**: VlocityNoRootNode
    - **Response JSON Path**: The name of the Omniscript Element receiving the value.
4. If needed, select **Apply if error** to enable actions that run successfully to apply their responses to the Omniscript's data JSON even when other actions in the Action Block fail.
5. When the Action Block is inside of a Step, set validation to **Step** to prevent the Action Block from running when errors exist in the Step.
6. Preview the Omniscript to test the Action Block behavior.