Troubleshooting Custom BIRT report performance

We solved our problem with some reports “stuck” in the BIRT queue.  Someone (nameless but not me) created some new BIRT reports for Maximo without using one of the Tivoli templates.  The report was missing the afterFactory code snippet:  

MXReportScriptContext.close();

So the BIRT report engine kept it in the queue indefinitely, even though the report had already been rendered for the user.