Continue Even on Error option
- Last UpdatedOct 23, 2024
- 1 minute read
This option indicates that the flow of the middleware execution will continue even when an error is encountered in any part of the execution sequence.
The table below describes the flow of the middleware call after the pre- or post-hook execution is completed with the Middleware Flow param\-eter set to Continue Even on Error.
|
Hook Type |
Middleware Execution Status |
Hook Success |
Hook Error |
|---|---|---|---|
|
Pre-Hook |
Not applicable. |
The pre-hook call is completed successfully. Note: The data modified on tables for the pre-hook call is committed. The middleware continues to execute the normal middleware call. |
Continue even on error. The pre-hook call resulted in an error. The generated error message is ignored by the middleware. Note: The data modified on tables for the pre-hook call is rolled back. The middleware continues to execute the normal middleware call. |
|
Post-Hook |
The normal middleware call/transaction has succeeded. |
The database transactions started for the normal middleware call and for the post-hook call are committed. |
The data modified on tables for the normal middleware call is committed, but the data modified on tables for the post-hook is rolled back. The error message generated by the post-hook transaction is ignored by the middleware. |
|
Post-Hook |
The normal middleware call/transaction has failed or rolled back. |
Stop. The error message is returned to the caller. Note: The post-hook will never be executed, because the normal middleware call/event/transaction has failed or rolled back. |
Not applicable. Note: The post-hook will never be executed, because the normal middleware call/event/transaction has failed or rolled back. |