When Until Successful Fails

An investigation into Error Handling when the Until Successful scope fails in the MuleSoft Anypoint Platform

Transcript

1. WHEN UNTIL SUCCESSFUL FAILS AN INVESTIGATION INTO ERROR HANDLING WITH THE UNTIL SUCCESSFUL SCOPE
2. DEFAULT SETUP • Asynchronous • Must configure object store first • Otherwise set to Synchronous, which cannot be used with an object store • In following tests, set to Synchronous
3. TEST I: SETUP • Success Flow (returns 200) • Fail Flow (returns 400) • Call Each to prove response
4. TEST I: RESULTS • Success200 • Fail400
5. TEST II: SETUP • Call the success endpoint, wrapped in processor chain & Synchronous Until Successful scope • Catch Errors and set payload to “Error has been caught” if there is an error
6. TEST II: RESULTS • Response is as expected
7. TEST III: SETUP • Call the fails endpoint, wrapped in processor chain & Synchronous Until Successful scope • Catch Errors and set payload to “Error has been caught” if there is an error
8. TEST III: RESULTS - LOGS • Returns org.mule.module.http.internal.request.ResponseValidatorException
9. TEST III: RESULTS - RESPONSE • Error caught and handled accordingly
10. TEST IV: SETUP • Common Context: Orchestration Strategy in Process API, when calling system APIs • Call Retry Success, log output • Call Retry Fail, log output • Attempt to set Payload (do more work) after failing endpoint • What do you think the response will be?
11. TEST IV: RESULTS - LOGS • Logs consistent as before, • Payload returned with error handling
12. TEST IV: RESULTS - RESPONSE • Processing Continues as the error was handled downstream in the flow. • Key Takeaway: • When work fails with Until Successful scope downstream, must handle the response explicitly if you want processing to stop!
13. HOPE THIS HELPS!