# ErrorReactionType (Complex Type)

### Namespace: http://midpoint.evolveum.com/xml/ns/public/common/common-3

What should a task do when an error of given type is encountered? Only some combinations of values are allowed: ignore (+ stopAfter), retryLater (+ stopAfter), stop.

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
ignore | container IgnoreErrorReactionType | [0,1] | Error should be ignored and the processing should continue.
stop | container StopProcessingReactionType | [0,1] | The processing should be stopped.
retryLater | container RetryLaterReactionType | [0,1] | Processing of the specified account should be retried later.
stopAfter | property int | [0,1] | Task is stopped after seeing this number of errors.

- ### Items

  - #### ignore

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Error should be ignored and the processing should continue. E.g. for live sync tasks, the token is advanced to the next item. The ignorance is not complete, though. For example, the error is recorded into the operationExecution item of the object being processed.

  - #### stop

    Flags: RAM,runtime

    Multiplicity: [0,1]

    The processing should be stopped. This is the default strategy for live sync and async update tasks.

  - #### retryLater

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Processing of the specified account should be retried later.

  - #### stopAfter

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Task is stopped after seeing this number of errors. TEMPORARY. Most probably will be replaced by the thresholds mechanism.