Can same assignment be assigned to different work queues?also is there a restriction to number of assignments assigned?-no

General
1

Can same assignment be assigned to different work queues?
and is there a restriction to number of assignments assigned?

2

In Pega, an assignment is typically routed to one operator or one work queue at a time.
So a single assignment cannot simultaneously belong to multiple work queues. However, you can achieve similar behavior by Re-routing the assignment from one work queue to another

Usually no — a guardrail warning is not a hard stop to. Pega gives guardrail warnings when a flow/process has too many steps/shapes because very large flows become:

  1. hard to maintain
  2. difficult to understand
  3. harder to test
  4. potentially less performant
3

1)Can the same assignment be assigned to different work queues?
No — a single assignment can belong to only one “owner” at a time, where the owner is either:
(a)An operator (Worklist), or
(b)A work queue (Workbasket)

So your statement is correct ! you cannot have one assignment simultaneously sitting in multiple queues.

How to achieve “multiple queues” behavior (Pega-recommended patterns)
(a)Re-route / Transfer the assignment to a different workbasket (ownership changes, still one assignment).
(b)Create multiple assignments (parallel work) if you truly need multiple queues/teams to work at the same time:
Use parallel flow / Split-Join / subprocess to create separate assignments, each routed to its own queue.
This is the clean, auditable way to support “same case, multiple queues.”

Best practice: If two queues must act independently, do not share one assignment—create two assignments and track outcomes explicitly.

2)Is there a restriction to the number of assignments assigned?
There is no fixed hard platform limit like “only N assignments per user” enforced out-of-the-box. The answer to this is based on the real-world expectation from CSR on throughput. Pega’s “restriction” is mainly operational and performance based, such as:
(a) Queue/Worklist performance (large workbaskets slow down reporting, list retrieval, and user productivity)
(b) SLA processing overhead (each open assignment may carry SLA and urgency calculations)
(c) Database growth (assignments/assignment history tables grow quickly)
(d)User experience (review/perform screens and inboxes become noisy if cases create excessive assignments)