I have created a scheduled job for a client - the job runs every 15 minutes and looks for order confirmations that need to be printed based on a certain criteria. It changes an optional field value on the order from 0 to 1 at the end of the job, so we know not to print that order the next time the job is run.

The job runs great - except when there is a large number of orders to print. (So if the job runs 20 orders, everything is fine. If the job runs 70 orders, we have issues.) Based on what I'm seeing, it looks like Iman is opening and running the OE Order Confirmation Printing screen individually for each order. So, it gets through a certain number of orders successfully and then we get an error: "Crystal Reports Error: Load report failed." Once this error is hit, we get the error for every record/order left to run in the job.

Imagine a scenario where the first 20 orders print and then the job throws this error: If I set the process to abort job on a transform error -- the flag for the orders that did print does not get updated. So 20 orders print, and all the flags are still set to 0, so the system will try to run them again next time, blow up again, not update, etc. (I'm in a continuing error loop.)  If I set the process to reject record, Iman seems to "stutter" and print some of the orders multiple times, and then it hits a wall and can't print any more of the orders. All of the print statuses get updated to 1 - whether the order printed or not.

I'm trying to figure out if I've set up the job incorrectly, or if I am asking Iman to do something it wasn't really meant to do. (I want to create additional jobs that use Iman to email out order confirmations as a pdf attachment to customers - but they send 300 emails a day right now, so if the OE Order Confirmation screen is going to throw load report errors, Iman would not be a good solution for this.)

Thanks for your help!