Support Article

BadInputException - Scheduled Tasks Obj-Delete-By-Handle

SA-28567

Summary



An error appears in the logs after a scheduled report is run. 

After the run completes, the system tries to clean up the generated file but a BadInputException is shown in the logs by an Obj-Delete-By-Handle step in the pyActionAttachFileToWO activity.


Error Messages



12 Sep 2016 00:01:01,624 [ PegaRULES-Batch-3] (edTask_OutputProcessing.Action) ERROR - Error in Obj-Delete-By-Handle
com.pega.pegarules.pub.database.BadInputException: Instance with handle DATA-WORKATTACH-FILE PEGA-SCHEDULEDTASK PX-ST-314!20160909T040056.159 GMT does not exist
From: (B96FFB8FCC7FA78CE78762C753D85A130)
at com.pega.pegarules.pub.database.BadInputException.createGenericBadInputException(BadInputException.java:185)
at com.pega.pegarules.data.internal.access.DatabaseImpl.lockBeforeDelete(DatabaseImpl.java:4161)
at com.pega.pegarules.data.internal.access.DatabaseImpl.delete(DatabaseImpl.java:4193)
at com.pegarules.generated.activity.ra_action_pyactionattachfiletowo_9513880afeebfcc9ac2c28f43286e508.step5_circum0(ra_action_pyactionattachfiletowo_9513880afeebfcc9ac2c28f43286e508.java:789)
at com.pegarules.generated.activity.ra_action_pyactionattachfiletowo_9513880afeebfcc9ac2c28f43286e508.perform(ra_action_pyactionattachfiletowo_9513880afeebfcc9ac2c28f43286e508.java:140)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10674)
at com.pegarules.generated.activity.ra_action_pytaskoutputprocessor_c5f98d3b8ab463756be76edd9707b570.step2_circum0(ra_action_pytaskoutputprocessor_c5f98d3b8ab463756be76edd9707b570.java:370)
at com.pegarules.generated.activity.ra_action_pytaskoutputprocessor_c5f98d3b8ab463756be76edd9707b570.perform(ra_action_pytaskoutputprocessor_c5f98d3b8ab463756be76edd9707b570.java:94)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10674)
at com.pegarules.generated.activity.ra_action_pzscheduledtaskprocessor_b029c8dee26cd2e59bc5d637377eb13f.step7_circum0(ra_action_pzscheduledtaskprocessor_b029c8dee26cd2e59bc5d637377eb13f.java:815)
at com.pegarules.generated.activity.ra_action_pzscheduledtaskprocessor_b029c8dee26cd2e59bc5d637377eb13f.perform(ra_action_pzscheduledtaskprocessor_b029c8dee26cd2e59bc5d637377eb13f.java:183)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:732)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:607)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:980)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1290)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1038)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:920)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:697)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532)
at java.lang.Thread.run(Thread.java:745)


Steps to Reproduce



Create a report with a long name through the Report Browser and schedule it to be sent out.
 

Root Cause



A defect in Pegasystems’ code, or rules was appending the pyNote to the file name causing the length of the name to exceed current restrictions.

Resolution



Apply HFix-29552 and follow instructions in the readme file. 

​A temporary solution is to rename the report name to a shorter name, but it could become unrecognizable by the user who created the report.

 

Published September 28, 2016 - Updated October 6, 2016

Have a question? Get answers now.

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