If an error occurs during the invocation of a Deferred Process, then the transaction surrounding this invocation will be rolled back (thus losing any updates to business entities). Once this rollback has occurred then the deferred processing engine starts another transaction, creates a row on this table to store the details of the error and commits the transaction.

The data on this table is then available to application error processing.

Example

You model a new deferred process. You also modify some online business logic to call the API to queue requests to invoke your Deferred Process.

User Ronan Rooney accesses an online function which calls your online business logic. The Cúram Server starts your deferred process by enqueuing a JMS message. Control returns to Ronan Rooney.

The queue manager dequeues the JMS message and invokes the deferred processing engine. The deferred processing engine attempts to invoke your Deferred Process but encounters an error. The deferred processing engine creates a row on this table to store the error.

Your custom processing reads this row and sends an email to User Ronan Rooney notifying him of the error.

Technical Notes

For more information see the Cúram Workflow Management System Developer's Guide.