---
title: "Workflow Do Nothing Rule (Queue Assignment Exists)"
slug: "do-nothing-rule-queue-assignment-exists"
status: "new"
updated: 2026-06-25T15:28:12Z
published: 2026-06-25T15:28:12Z
canonical: "knowledge.technolutions.net/do-nothing-rule-queue-assignment-exists"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow Do Nothing Rule (Queue Assignment Exists)

Create a do nothing rule when manually selected workflow queue assignments are being cleared after rules run. The rule catches records that already have a queue assignment in the workflow and prevents later bin movement rules in the same exclusivity group from reapplying workflow, bin, or queue assignments.

This configuration is useful for workflows where reviewers or staff use manual queue assignment, including the **Add to Queue** option in Reader.

> [!TIP]
> ⭐ Get Inspired
> 
> This article was adapted from [a post by Technolutions staff](https://community.technolutions.net/get-inspired/post/building-a-do-nothing-rule-for-queue-assignments-in-the-workflow-editor-m7eMhSAkqHmd2Ig) in the Slate Community Forums' Get Inspired space. Have a great idea for a Get Inspired post? [Let us know](https://community.technolutions.net/get-inspired/new?post_type=gnHx7As1gZ8r6Ld)!

## Creating the rule

1. Go to the workflow exclusivity group that controls bin movement.
2. Select **New Rule**.
3. Enter a descriptive name, such as **Do Nothing If Queue Assignment Exists**.
4. Use the same Configurable Joins base and rule type as the other rules in the exclusivity group.
5. Leave the rule trigger set to **Upon Update (Deferred)**, unless your workflow design requires a different trigger.
6. Confirm that the correct exclusivity group is selected.
7. Set the rule as deterministic with an exclusive priority.
8. Enter a low, unique priority number so this rule runs before bin movement rules.
9. Select **Save**.

![Rule settings for a Do Nothing If Queue Assignment Exists workflow rule](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/01-DIS35P8tvmsdHgsB4rb91.webp)

## Adding a subquery filter for queue assignment existence

1. Select **Subquey** **Filter**.
2. Enter a clear name, such as **Queue Assignment in App Review Workflow Exists**.
3. Leave **Type** set to **Dependent subquery**.
4. Leave **Aggregate** set to **Exists**.

![Dependent subquery filter configured with Exists aggregate for queue assignment logic](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/02-YkipeIrGojWn5SmQlmMIK.webp)

## Joining to the workflow queue

1. In the subquery filter, select **Join**.
2. Under **Application**, select **Workflow Bin User Queue**.
3. Select **Continue**, then select **Save**.

This join limits the rule to records with an existing queue assignment.

![Join selection for Workflow Bin User Queue under the Application heading](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/03-w8FXWLzvdv5BFsqYNSzOr.webp)

1. From the same subquery filter, select **Join** again.
2. Under **Workflow Bin User Queue**, select **Workflow**.
3. Select **Continue**, then select **Save**.

![Join selection for Workflow under the Workflow Bin User Queue heading](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/04-lAxBkwOzsBHIteZw045HF.webp)

## Filter to the current workflow

1. In the subquery filter, select **Filter**.
2. Select **Name**.
3. Leave the operator set to **IN**.
4. Select the workflow that the exclusivity group supports.
5. Select **Save**.

![Workflow Name filter limited to the current workflow](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/05-4Q8lcZ95HtMiMnPxJ3dgI.webp)

## Set the rule action

1. Select **Save** to finish the subquery filter.
2. In the rule action section, select **No Action Rule**.
3. Save the rule.
4. When ready, edit the rule and set **Status** to **Active**.

When a record meets this rule, later rules with higher priority numbers in the same exclusivity group are skipped. The record keeps its existing queue assignment.

![No Action Rule selected in the rule action section](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/06-JZGYKVo8IaSixwqgvKpCZ.webp)

> [!TIP]
> ⭐ Best practice
> 
> Create one do nothing rule for each workflow exclusivity group where existing manual queue assignments should be preserved.

For more information, see [Workflows](https://knowledge.technolutions.net/docs/workflows) and [Exclusivity Groups](https://knowledge.technolutions.net/docs/exclusivity-groups).