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

Scheduled Task is not triggering after a schedule update

SA-1998

Summary


The Administrators had received reports that people were not receiving scheduled reports after making a modification to the Scheduled Task.

On investigation it was observer that when the Scheduled Task was cancelling then re-enabling the row that gets inserted into pr_sys_queues contains blank information on: - 

pxCreateDateTime 
pxLastExecutionDateTime 
pyAgentName 
pySelectId 
pyPriority 


In particular with the blank pyAgentName this means that the ScheduledTaskProcess agent will never process that row.

Steps to Reproduce


1. (Optional) stop all agents 
2. And ensure the ScheduleTaskProcess agent is stopped (not optional) 
3. Log into the Case Manager portal 
4. Go to the Reports tab 
5. Right click on a report (that doesn't have a schedule) and click on the "Schedule" button 
6. Create a Daily Scheduled report, choosing today's date as the starting date. 
7. (Optional through to and including step 11) By default you will need to set the first run at some full hour in the future. 


In SQL (Oracle in this instance) update the pr_sys_queues so that the report will be run immediately 
 
update pr_sys_queues set pxMinimumDatetimeForProcessing = sysdate where pxinsname like 'SYSTEM-QUEUE-SCHEDULEDTASK 14102%' 
commit 

You may need to examine your instance data to know which row to run 
HINT: By default Oracle doesn't display the time portion of a date time. But the query below will show this:- 
 
select to_char(pxcreatedatetime,'DD/MM/YYYY HH24:MI:SS') createdate, pxinsname, 
to_char(pyminimumdatetimeforprocessing,'DD/MM/YYYY HH24:MI:SS') mintime, 
to_char(pxlastexecutiondatetime,'DD/MM/YYYY HH24:MI:SS') lastrunat, pxobjclass, 
pyagentname, pxprocessingnodeid, pyattempts, pymaxattempts, pyitemid, 
pyitemstatus, pzinskey, 
pyselectid, pypriority 
from pr_sys_queues 
where pxinsname like 'SYSTEM-QUEUE-SCHEDULEDTASK 14102%' 


8. In SMA: Go to Agent Management > Agents and start the ScheduledTaskProcess agent 
9. In SQL: Re-examine the pr_sys_queues entry. This should show that the pyMinimumDateTimeForProcessing has been updated to tomorrow 
10. If you have configured an email server then you should have also received an email. 
11. In SMA: Stop the ScheduledTaskProcess agent 
12. In PRPC Developer portal: From the Pega button choose Reporting > Components > Scheduled Tasks 
13. Open the newly created Schedule Task 
14. Click on the Update button 
15. Then click on the Delete button 
16. In SQL: Run the query against pr_sys_queues. This should show that the row has disappeared 
17. In Case Manager portal : Refresh the screen. 
18. Right click on the same report and click on the "Schedule" button. 
19. Click on the Reopen button 
20. Click on the Submit button. 

21. In SQL: Examine the row and verify that some of the required columns are blank.

Root Cause


This was identified as defective behaviour.


Resolution


HFix-10000 is available to address this.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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