Miscellaneous actions

  • Last update on February 23rd, 2024

Miscellaneous” actions are native CoreView actions that, together with “Manual” actions are specifically dedicated to workflows. They can only be accessed from the Manage workflow” section.

This article will examine in detail the capabilities of each of these workflow management actions. 


This action allows you to configure how many minutes a workflow should wait before executing the following action. Adding a “Delay” action to a workflow can be useful to allow sufficient time for technical execution between one action and the next. 

Execute nested workflow

This action enables you to execute a workflow within another workflow. Typically, it is configured to run only if a specified filter parameter is met. Let's view an example:

  1. The first action is a “Multichoice with timeout” that sends an approval request to execute the nested workflow.
  2. If approved, the nested workflow is executed. If rejected, the nested workflow will be skipped due to the configured filter.
  3. The workflow executes the following actions.
  4. A confirmation email is sent to the admin.

Let's view how to configure a nested workflow like the one in the example above:

Step 1: Configuration

Add a new Miscellaneous action, select “Execute Nested Workflow” and pick the desired workflow. In this example, the selected nested workflow removes all tags from the user(s).

Step 2: Schedule when workflow starts (optional)

You can schedule your nested workflow by switching on the “Schedule when the workflow starts” toggle and setting a delay of up to 90 days. This feature not only boosts performance, but also optimizes your action execution limit by dividing workflows into two: one that completes, and another that starts as scheduled. 

Step 3: Add execution input

Insert the required execution input, in this case it's the user principal name, and press “Save”.

Step 3: Add filter

Add a filter to the “Execute Nested Workflow” action that only executes the workflow if the answer to the multichoice email request is “yes”. 

Nested workflow vs. 50 workflow execution limit

When dealing with nested workflows, it's important to consider them as single entities. This means that if you have a workflow containing two nested workflows, you count a total of three workflows: the parent workflow, the first nested workflow, and the second nested workflow.

In addition, when you have more than 50 workflows running concurrently, we manage them through two different queues. The normal queue contains all the workflows that are not nested, while the Priority queue is designated for nested workflows. When available, we select the first workflow from the Priority queue and continue to process workflows from there until the queue is empty.

Now, let's illustrate these rules with a use case:

Imagine you are running 49 workflows simultaneously, and you initiate the execution of the 50th workflow, which contains two nested workflows (Nested1 and Nested2). The parent workflow will run as the 50th in the queue.

As soon as the nested workflow action starts within the parent workflow, we place Nested1 in the priority queue. However, Nested1 won't begin execution immediately because there's no available space due to the 50th parent workflow still running. To address this, we temporarily suspend the parent workflow while Nested1 is in the priority queue. Once the parent workflow is in the sleeping state, Nested1 can start its execution, following the same rule applied to Nested2.

Retrieve data from object

This action enables you to gather specific pieces of information from an item, which can then be used as input variables within your workflow. 

Please visit Retrieve data from object: a practical example to learn more. 


This action terminates a workflow. It is frequently used in combination with a filter that forces the workflow to stop under certain conditions.

In the example below,  the workflow is configured to halt based on the user's response to the “Multichoice with timeout” action, which is scheduled at the beginning: 

Step 1: Configuration

In this example, the “Stop” action is configured to only be executed if the answer to the “Multichoice with timeout” action is “no”.

Add a new action under the “Miscellaneous” category, select “Stop”, and press “Save”.

Step 2: Add filter

Add a filter to the “Stop” action that only executes it if the answer provided is “no”.

Step 3: Execution

Run the workflow. The designated decision maker will get an email with the multichoice question.

Step 3.1: Rejection

Let's select “no”.

In the “Execution detail” panel, we see that the “Stop” action has been executed, hence terminating the workflow. The workflow will appear as “Succeeded”.

Step 3.2: Approval

Now let's run the workflow again and select “yes”.

This time, the “Stop” action has been skipped and the subsequent actions have been executed instead.