Skip to content

Update work-queues-known-limitations.md #1738

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update work-queues-known-limitations.md #1738

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9842323
Update work-queues-known-limitations.md
kenseongtan May 26, 2025
463f189
Update work-queues-known-limitations.md
DanaMartens May 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion articles/desktop-flows/work-queues-known-limitations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Known limitations for work queues
description: Known limitations for work queues.
ms.topic: article
ms.date: 03/10/2025
ms.date: 05/27/2025
ms.author: appapaio
ms.reviewer:
contributors: DanaMartens
Expand All @@ -20,6 +20,7 @@ The following table lists known limitations for work queues in Power Automate fo
| Work queue connector disabled in GCC High and DoD environments | The work queue connector that is applicable to Power Automate for desktop only, is disabled by default for customers operating in GCC High and DoD environments. | You can enable the work queue connector and its actions. More information: [Disable new connectors by default in GCC High and DoD](/power-platform/admin/connector-off-by-default). |
| Work queue DLP policy configuration support | There may be a delay before new work queue connector actions added to Power Automate desktop are visible and configurable through DLP policies in Power Platform Admin Center. <br><br>Additionally, if you want to limit the use of work queues in cloud flow and API-based scenarios, you should use Dataverse RBAC to control access to the underlying tables. This is because work queues are built on the Dataverse platform, and their actions (such as adding, updating, deleting and dequeueing) are accessible by-design through the native Dataverse connector, which cannot be completely blocked by DLP policies. |
| Throughput and scaling | Work queues aren't suited for high throughput (subsecond processing time) scenarios, where hundreds or thousands of items need to be processed in seconds. If you do have such throughput requirements, consider using other queuing solutions such as Azure Service Bus Queues. |
| [Work queues SLA](../work-queues-manage.md#work-queues-sla) | When you add an SLA configuration to an existing work queue that previously didn’t have one, the SLA status isn't computed unless the work queue has no queued items. | To ensure SLA status computation works correctly, create a new work queue with SLA configured, or ensure that the existing work queue doesn't have any item in queue the first time you configure SLA for your work queues.|

## Related information

Expand Down