After upgrading to Utah last week, our scheduled RPA bots have stopped executing automatically. The bots run perfectly when triggered manually through the RPA Hub interface, but the scheduled executions don’t fire at all. We have five bots scheduled to run daily at different times - none are executing on schedule.
I’ve checked the bot schedules in RPA > Bot Executions > Schedules and they all show as Active with correct cron expressions. The scheduler service (sn_rpa_scheduler) appears to be running in the instance. Bot execution history shows only manual runs since the upgrade, with no scheduled attempts logged. No errors in system logs related to RPA scheduling.
The bots handle invoice processing, data extraction, and report generation - all critical daily operations. We’re currently running them manually which defeats the automation purpose. Has anyone experienced scheduler issues after Utah upgrade? Is there a configuration change or service that needs reinitialization?
Utah introduced a new property for RPA scheduler timezone handling. Check System Properties > RPA and look for ‘sn_rpa.scheduler.use_user_timezone’. If this is set to true but your scheduler user doesn’t have a timezone configured, schedules won’t trigger. Either set a timezone on the scheduler user account or change this property to false to use system timezone. This caught me off guard during our upgrade testing.
Beyond timezone, verify your bot schedules weren’t corrupted during upgrade. Sometimes the schedule refresh process fails silently. Go to each bot’s schedule configuration and click ‘Refresh Schedule’ button. This regenerates the schedule execution plan. Also check if you have any custom business rules on the sn_rpa_bot_schedule table that might be blocking automated execution.
Checked the scheduled job - it’s running every 5 minutes as expected with no errors. The sn_rpa_scheduler_user account is active with correct roles (rpa_admin, schedule_admin, and itil). Still no scheduled executions. Could this be timezone related? Our instance timezone is EST but the bot schedules show UTC times.
I encountered this after our Utah upgrade too. The issue was that the RPA scheduler user account lost some permissions during the upgrade. Navigate to User Administration and verify that the ‘sn_rpa_scheduler_user’ system account has the correct roles: rpa_admin and schedule_admin. Also check if the account is active and not locked. After fixing permissions, I had to restart the scheduler service through the application registry.
I’ve resolved this exact issue on three Utah instances now. The problem stems from changes in how the RPA scheduler service handles schedule processing after the upgrade. Here’s the complete solution:
RPA Scheduler Service:
Utah modified the scheduler service initialization sequence. The service starts successfully but doesn’t properly register schedule listeners. To fix:
Navigate to System Applications > Application Registry
Find ‘RPA Hub’ application
Click ‘Restart Application’ - this reinitializes all RPA services including the scheduler
Wait 10 minutes for full service restart
After restart, verify the scheduler job: System Scheduler > Scheduled Jobs > ‘RPA Bot Schedule Processor’. It should show recent execution history with no errors.
Bot Schedule Refresh:
Utah requires manual schedule refresh after major upgrades due to schema changes in the sn_rpa_bot_schedule table. For each bot:
Navigate to RPA > Bot Executions > Schedules
Open each active schedule
Click ‘Refresh Schedule’ button at the top
Verify the ‘Next Run Time’ updates to a future timestamp
Check ‘Schedule State’ field shows ‘Ready’ not ‘Pending’
The refresh regenerates the execution plan with Utah’s new scheduler format. Without this, old schedule formats aren’t recognized by the new processor.
Time Zone Configuration:
Utah added timezone awareness to RPA schedules. Critical changes:
System Property: Set ‘sn_rpa.scheduler.use_user_timezone’ to false (System Properties > RPA)
This forces system timezone usage for consistency
Default changed to true in Utah which breaks schedules if scheduler user lacks timezone
Verify system timezone: System Properties > System > ‘glide.sys.default.tz’
Should match your operational timezone (e.g., ‘America/New_York’)
RPA schedules now respect this instead of always using UTC
Update bot schedules if needed: If you want to keep user timezone mode (property = true), set timezone on the sn_rpa_scheduler_user account:
User Administration > Users > sn_rpa_scheduler_user
Set Time Zone field to match system timezone
Verification Steps:
Check System Logs: System Logs > System Log > All
Filter: Source contains ‘rpa’ AND Created after upgrade date
Look for ‘Schedule processor initialized’ message
Test immediate execution: Change one bot schedule to run 5 minutes from now
Monitor: RPA > Bot Executions > Execution History should show scheduled run
After following these steps on our three instances, all scheduled bots resumed normal operation within 15 minutes. The application restart is the key step - it’s not documented in the Utah upgrade guide but is essential for RPA scheduler functionality. If issues persist, check for custom business rules on sn_rpa_bot_schedule or sn_rpa_execution tables that might have before-insert conditions blocking scheduled runs.
Check if the RPA scheduler job is actually running. Go to System Scheduler > Scheduled Jobs and search for ‘RPA Bot Schedule Processor’. It should run every 5 minutes. If it’s not executing, try manually running it once to see if it kicks off your bots. Utah changed some scheduler dependencies.