Ignoring failures
By default, if any synchronous event handler reports a failure, the system skips any remaining event handlers for that application event and exits with a status of .
To override this default behavior, on the Event Handlers form, select the check box.
If you select this option, the event handler is always treated as successful unless an illegal operation is deliberately attempted. However, in the Status field of the Event Handler Status form, the status remains , even though the check box is cleared on the Event Status form.
This table shows what conditions can result in failures for various action types and whether the failure can be ignored.
| Action type for the current event action | Condition | Ignore Failure option selected? | Result (Event Status) |
|---|---|---|---|
| Set Values | Illegal operation: Any attempt to set a non-output event parameter | N/A | Failure |
| Some | Illegal operation: Any attempt to use an action type that is not supported on the current tier | N/A | Failure |
| Any | Illegal operation: Syntax error in parameter | N/A | Failure |
| Generate Event | Illegal operation: Any attempt to generate a framework event | N/A | Failure |
| Any | Unexpected error | No | Failure |
| Any | Unexpected error | Yes | Success |
A action whose condition evaluates to True on an event handler for which the option is selected is equivalent to a action.
An asynchronous event handler's failure does not affect any remaining event handlers for that event. However, setting the option in this case avoids affecting the AnyHandlersFailed() attribute of that event, unless the failure was caused by deliberately attempting an illegal operation, as shown in the table.