Database Failures During Communications Inbound Receiver Processing

The following process describes what happens when a Siebel database fails during Communications Inbound Receiver processing:

1. The driver generates an event for Communications Inbound Receiver.

2. Communications Inbound Receiver creates a .evt file that stores the driver event.

3. Communications Inbound Receiver renames the .evt file to .xevt immediately before workflow execution.

4. The workflow returns an error, and Communications Inbound Receiver determines the Siebel database is down.

5. Communications Inbound Receiver renames the .xevt file to .paused.

6. Within five minutes, the event is renamed from .paused to .evt and requeued.

The figure in Event Processing illustrates this process in the illustration lines with a notation of C.