RPA bot fails to trigger on scheduled batch process for docu

BPM Pega Platform
, , , , , , ,
1

We’ve configured an RPA bot to process document extraction during nightly batch runs. The bot is supposed to trigger at 2 AM daily to process invoices that accumulated during the day. However, the bot frequently fails to start at the scheduled time.

When I manually trigger the bot through the RPA Studio, it executes perfectly and processes all pending documents. But the scheduled batch trigger is unreliable - sometimes it works, sometimes it doesn’t. There’s no consistent pattern to the failures.

I’ve checked the scheduler configuration and it appears correct with the cron expression set for 2 AM daily. The bot work group assignment looks fine as well. The batch trigger validation doesn’t show any obvious errors. Has anyone experienced similar issues with RPA bot scheduling in Pega 8.5 batch processes?

2

I’ve troubleshot this exact issue several times. The problem typically involves a combination of configuration issues across the scheduler, work group, and bot assignment. Here’s the comprehensive solution:

Scheduler Configuration: First, verify your Job Scheduler setup. Navigate to Designer Studio > Integration-Resources > Job Scheduler and locate your RPA batch job. The cron expression for 2 AM daily should be: 0 0 2 * * ?. However, the schedule alone isn’t enough - you need to ensure the job’s activity properly triggers the bot.

The activity that the scheduler calls should not directly start the bot. Instead, it should create work items (cases or assignments) that the bot will pick up. The scheduler should trigger an activity that queries for pending documents and creates a queue of work items. Then configure your bot to monitor this queue and process items as they appear.

Bot Work Group Assignment: This is often the root cause. Go to the RPA Administration portal and check your work group configuration. Your bot needs to be assigned to a work group that has active runtimes available at 2 AM. Verify these settings:

  1. Work group has at least one runtime configured
  2. Runtime availability schedule includes your batch window (2 AM - whenever processing completes)
  3. The runtime machine is actually powered on and connected at 2 AM
  4. Work group assignment rule matches your bot’s requirements

If your runtime machines are virtual and get shut down overnight for cost savings, this would explain the intermittent failures. Ensure the runtime infrastructure is available 24/7 or adjust your schedule to match when runtimes are guaranteed to be active.

Batch Trigger Validation: The most reliable approach is to use a queue-based trigger rather than a direct schedule trigger. Modify your architecture:

  1. Scheduler creates a batch work item at 2 AM
  2. This work item contains the list of documents to process
  3. Bot monitors a specific queue for batch work items
  4. When the work item appears, bot picks it up and processes the documents

This decouples the scheduling from the bot execution, making it more reliable. Configure your bot with a “Queue Item” trigger type rather than “Schedule” trigger. The bot continuously monitors the queue (or checks every few minutes) and processes items as they arrive.

To implement this, create a case type for batch processing jobs. Your scheduler activity creates an instance of this case type at 2 AM. Configure your bot to query for cases of this type with status=“Ready for Processing” and process them sequentially.

Additionally, add proper error handling and logging. In your bot configuration, enable detailed logging and configure it to write to a specific log file for batch runs. This will help you diagnose future issues. Also implement a notification mechanism - if the bot fails to start within 15 minutes of the scheduled time, send an alert email to the operations team.

One final critical point: check your Pega system’s background processing node configuration. If background processing is disabled or limited during off-hours, this could prevent the bot trigger from working. Ensure that the node where your RPA runtime is registered has background processing enabled 24/7 or at least during your batch window.

3

Another thing to check is the bot’s authentication configuration. If your bot needs to authenticate to external systems and the credentials expire or aren’t available during the scheduled run, the bot might fail to start. Also, make sure the batch process isn’t timing out before the bot can initialize - some bots take a few minutes to fully start up, and if the batch job has a short timeout, it might abort before the bot actually begins processing.

4

Look at your Job Scheduler logs in the system management application. The logs will show whether the scheduler is actually firing the job at 2 AM or if there’s an issue with the schedule itself. Also check if there are any queue processor rules that might be interfering with the bot execution. Sometimes queue processor priority settings can cause delays or prevent execution if system resources are constrained.

5

This sounds like a work group availability issue. When the scheduler triggers the bot, it needs to assign it to an available runtime in the work group. If no runtime is available or the work group configuration doesn’t match the bot’s requirements, the bot won’t start. Check your work group settings and ensure that at least one runtime is configured to be available during your scheduled batch window. Also verify that the runtime’s capabilities match what the bot requires.

6

Check if your RPA runtime is actually running at 2 AM. Sometimes the runtime service might be stopped or restarted during off-hours for maintenance. Also verify that the bot queue has available capacity - if all bot runtime slots are occupied by other processes, your bot won’t start even if the schedule triggers correctly.