Failure Errors During Communications Inbound Receiver Processing
The following process describes what happens when a failure error occurs during Communications Inbound Receiver processing:
The driver generates an event for Communications Inbound Receiver.
Communications Inbound Receiver creates a .evt file that stores the driver event.
Communications Inbound Receiver renames the .evt file to .xevt immediately before workflow execution.
A failure occurs during email processing.
When Communications Inbound Receiver restarts, the .xevt file is found and renamed to .retry.evt.
The following warning message is logged: Event %s may have caused crash, requeueing event for one retry.
The event is requeued for processing.
The figure in Event Processing illustrates this process in the illustration lines with a notation of D.
Typical Processing of an Event that Previously Caused a Failure
The following process describes the typical processing of an event that previously caused a failure:
Communications Inbound Receiver renames retry.evt to retry.xevt immediately before workflow execution.
The workflow executes without error and retry.xevt is deleted.
The figure in Event Processing illustrates this process in the illustration lines with a notation of D1.
Processing of an Event that Caused a Second Failure
The following process describes what happens the second time an event causes a failure:
Communications Inbound Receiver renames retry.evt to retry.xevt immediately before workflow execution.
A failure occurs during workflow execution.
When Communications Inbound Receiver restarts, the retry.xevt file is found and renamed to .crash.
An email is sent to the administrator, and the following error message is logged: Event %s may have caused crash, change .crash extension to .evt to requeue on restart.
The figure in Event Processing illustrates this process in the illustration lines with a notation of D2.