If a process encounters a problem within a given activity, the process flow halts at the activity. One of two things occur.
See also: Process Errors
A number of internal and external operations provide error-handling retries to respond automatically should your application or network experience minor disruptions due to time-out errors, such as a very heavy transaction load.
The transaction is only retried when no data has been updated or changed.
xpath*()functions suffer an internal time-out error with a transaction that can be safely retried, the transaction is retried automatically.
Should an error occur, automatic retries occur at approximately the following intervals after each subsequent error. The interval between retries roughly doubles after each attempt.
If the retry that occurs after the last interval fails, no additional retries occur.
It is not possible to predict exactly when a subsequent retry occurs, due to the variable time spent retrying and catching each new error.
Retries are logged at the
Debug level in the engine server logs.
Final retries are logged as errors.
See also: Application Engine and Gateway Logging
On This Page