Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Troubleshooting errors in bulk processing

Updated on March 29, 2022

When you process cases in bulk, you might encounter errors. To resolve common issues that prevent you from processing multiple cases, follow the respective guidelines for each problem scenario.

The following are the most common issues that can occur during bulk question imports:
  • The Operator menu of your portal does not contain the Bulk actions option.
  • The list of items to bulk process is read-only.
  • The Processing Results column displays a failed status.
  • The Processing Results column never displays a status.
  • The Instruction column displays errors.
  • You receive no notification when background processing is complete.
  • The list of flow actions in the Select Action list is incomplete.

Condition

Users want to create or update cases, or run flow actions on multiple cases. One of several problems prevents users from processing cases.

Cause: The Operator menu of your portal does not contain the Bulk actions option.

Note: Only Pega Platform applications that you build with UI Kit support bulk processing.

Solution: Granting the appropriate privileges to your operator.

  1. Associate a role with your access group that grants you the Work-.PerformBulk privilege. For more information, see Granting privileges to an access role.
  2. Refresh your browser session.

Cause: The list of items to bulk process is read-only because another user has a lock on some cases.

Solution: Coordinating your work on cases with other users.

  1. Hover over the Lock icon in the list of cases to see the name of the user who currently has the case open.
  2. Contact the user to coordinate an appropriate time for you to bulk process the case.
  3. After the user releases the lock, click Update to refresh the list.

Cause: The Processing Results column displays a failed status.

Solution: Resolving bulk processing errors.

  1. Hover over the failed status to view an error message.
  2. Follow the instructions in the error message to resolve the issue.
  3. Rerun the bulk action.

Cause: The Processing Results column never displays a status.

Solution: Enabling the bulk processing agent.

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the SysAdmin category, and then click Agents.
  3. In the list of agents on your node, click the Pega-ProCom agent.
  4. On the Schedule tab, in the Scheduled Agents list, add the AgentBulkProcessing activity, and then select the Enabled check box for this activity.
  5. In the Agent-Wide Settings section, select the Enable this agent check box.
  6. Click Save.

Cause: The Instruction column displays errors.

Solution: Resolving assignment errors.

  1. In the header of Dev Studio, click ConfigureCase ManagementToolsWork AdminWorklist Assignment Errors.
  2. In the Assignments with errors window, review the list of problem assignments and their corresponding error messages to determine which errors you can clear.

Cause: You receive no notifications when background processing is complete.

Some flow actions support background processing, which can help you complete your work faster when you run a flow action for many cases. As a result, an agent queues each request and sends you an email when processing finishes. For more information, see Queue processor rules.

Solution: Configuring the email account

  1. Ensure that the Default email account is correctly configured in your application. For more information, see Creating an email account.
  2. On your Operator form, verify that the Email field contains a valid email address.

Cause: The list of flow actions in the Select Action list is incomplete.

Note: The Select Action list displays only flow actions that are visible to your current work pool and that have a common ancestor class to the cases that you are processing in bulk.

Solution: Configuring the display of flow actions.

    Complete any of the following steps:

  1. Display a flow action that is disqualified from bulk processing:
    1. In the navigation pane of Dev Studio, click Records.
    2. Expand the Process category, and then click Flow Action.
    3. Open the flow action that is missing from the Select Action list.
    4. On the Action tab of the Flow Action form, in the Indicator section, clear the Disqualify this action from bulk processing check box.
    5. Click Save.
  2. Display flow actions for cases:
    1. On the Bulk actions page, in the Filter Property column, remove the filter criteria that evaluate an assignment.
    For example: Delete rows that contain Assigned to Operator or Assigned to Work queue filter properties.
    1. Click Filter Cases.
    2. Select the check box next to each case for which you want to run the flow action.
  3. Display flow actions and connector actions for assignments:
    1. On the Bulk actions page, in the Filter Property column, add filter criteria that evaluate an assignment.
    For example: Add rows that contain Assigned to Operator or Assigned to Work queue filter properties.
    1. Click Filter Cases.
    2. Select the check box next to each assignment for which you want to run the flow action.

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us