Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

'GETNEXT' is not pulling any work even though the WB has work



A work basket has more than 100 cases for SKILL A and SKILL B users. When the USER with SKILL B hits the GETNEXT, the screen indicates there is no work.

The SQL that selects the work appears to restrict the results prior to applying the Skill filter. This prevents large work baskets from being processed.

Error Messages

Not Applicable

Steps to Reproduce

  1. When the first 50 of the most urgent work items in a work basket which do not have any work for a specific skill.
  2. Click "Get Next"
  3. The query returns no rows, resulting  the message ‘no work available’

Root Cause

This is the expected behavior for the legacy configuration of GetNextWork.


For help configuring GetNetWork on the Product Discovery Network (PDN) see:


Published April 11, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us