If namespace is null, audit trail entries from any flow chart are returned.]]> Only those flow charts that contain a timer trigger with a scheduled trigger date within the specified time range are included in the result. Note that if a timer trigger's scheduled trigger date has not been set, that timer trigger is not included in the forecast.

Returns a ForecastElement for each timer trigger in each flow chart that has a non-null scheduled trigger date. Note that if a flow chart contains more than one timer trigger with a scheduled trigger date set, there will be more than one entry in the iterator for that flow chart.

Note that the actual firing of flow charts may not directly correspond with the forecast due to a variety of factors.]]> If namespace is null, log entries from any flow chart are returned.]]> Usernames and role names must be unique within a group.]]> Usernames and role names must be unique within a group.]]> Note that calling clear() from within a running job will fail, because at the next transaction break, the engine will see that the job was deleted and rollback the transaction. Rolling back the transaction will undo the work of the clear() method. A simple workaround is to fork a new thread from within the running job, have that thread call Engine.clear(), and wait for the thread to finish. This solution works because the new thread uses a new database connection to perform its work.

If a flow chart is running when clear() is called, that flow chart will not terminate until the next transaction break, at which point the flow chart's transaction will rollback and the flow chart will terminate. To force early termination, interrupt the flow chart.]]>