Recurring schedule to finalize Outbound DB Template doesn't work
An outbound database template rule is scheduled to Finalize everyday. Data is written to the destination table during the first execution. However, the second execution is not initiated. This occurs because a broken queue item is generated after the first scheduled execution.
<pxErrorMessage>Table SOMETABLE does not exist in database ExternalMKTData</pxErrorMessage> is being found in the broken queue item xml of type System-Queue-ScheduledTask.
Steps to Reproduce
- Create an outbound database template rule.
- In the Finalize tab of the rule, configure a recurring schedule.
- Use the database template in an Offer flow or a Campaign.
- Run the campaign. Verify the first Finalization of the rule at the scheduled time and verify if data is loaded in the destination table. Check the broken queue item (System-Queue-ScheduledTask type). Verify if the rule is finalized and written to the second schedule.
A defect in Pegasystems’ code or rules.
There is no StepStatusFail handling in the Obj-Open of the finalized class' database table rule or a check if the database table existed. That is, if the FIRST finalization is performed through the schedule, the StepStatusFail (as the 'old' finalized class does not exist) is triggered. Therefore, the queue item used for the next execution is resaved in a Broken-Process state due to an invalid Final activity status.
0% found this useful