1. Mule
  2. MULE-5897

As a user I want to the ability to stop a flow when an error occurs during normal flow processing if the exception is of a specific type


    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 3.3.0
    • Fix Version/s: 3.3 M3
    • Labels:
    • User impact:
    • Similar Issues:
      MULE-5893As a user I want to be able to continue processing a message when an error occurs returning the result of processing as a response
      MULE-5894As a user I want to be able to use different error processing paths based on exception type or message contents
      MULE-5986As a user I want to the ability to rollback current transaction and send a notification about the message at the time of the exception
      MULE-5908As a user, I want complete and well-organized documentation on Flows
      MULE-5916As a user I want to be able to propagate SOAP faults and that they can also be handled by the exception strategy
      MULE-5898As a user I want to the ability rollback/commit a transaction in progress in a very intuitive way and based on exception type or message contents
      MULE-5896As a user I want to be able to define multiple named global exception strategies that can be referenced from and used by multiple flows
      MULE-5895As a user I want to be able to define a custom default exception strategy that is used when a a flow or service does not define one explicitly
      MULE-5901As a user I want session scope properties I set to be available in all flows that process the same message
      MULE-5899As a user I want much improved documentation for Mule 3.1/3.2 on how to configure the default-exception-strategy element to achieve common use cases


      Use cases

      Start execution by reading a file inbound endpoint, process it and send it to an HTTP endpoint. In case of a ConnectTimeoutException then stop current flow and notify

      Acceptance Criteria

      • An exception strategy can be configured such that when one type of exception (tested with instanceof) matches a flow is stopped.
      • All other exception strategy functionality should be supported alongside this functionality including performing different error path processing based on exception type.


        No work has yet been logged on this issue.


          • Assignee:
            Pablo La Greca
            Daniel Feist
          • Votes:
            1 Vote for this issue
            1 Start watching this issue


            • Created: