When using a flow-ref to call a flow that has it's processing strategy to be explicitly asynchronous from a synchronous flow will result in error:
org.mule.api.MessagingException: Unable to process a synchronous or non-blocking event asynchronously.
Calling an explicitly or default asynchronous flow from a synchronous flow will result in error as one cannot tell if the processing should be decoupled from the synchronous process or not. Therefore the actual design on Mule throws an error.
If you need the process result of the secondary flow then you must call another synchronous flow or sub-flow (which is processed synchronously using same thread from main flow).
Now, if you just want to send the copy of your payload to another flow without the need to get its processing result, you can then achieve it against an asynchronous flow if you use one of the following strategies:
Important to highlight here that for the case of using async component or vm transport, the result of the process of the secondary flow will not be used by the main one "support-synchronous-process-strategy-flow" as the async component will trigger in a separate thread while the main thread of the flow will proceed. Below the logging result and the request result of the test related to the images above for reference:
➜ test-maven-app curl http://0.0.0.0:8081 PAYLOAD1% INFO 2018-04-27 17:54:56,541 [[support-sync-async].HTTP_Listener_Configuration.worker.01] org.mule.api.processor.LoggerMessageProcessor: BEFORE ASYNC INFO 2018-04-27 17:54:56,541 [[support-sync-async].HTTP_Listener_Configuration.worker.01] org.mule.api.processor.LoggerMessageProcessor: AFTER ASYNC INFO 2018-04-27 17:54:56,544 [[support-sync-async].support-asynchronous-process-strategy-flow.stage1.01] org.mule.api.processor.LoggerMessageProcessor: TEST2 INFO 2018-04-27 17:54:56,556 [[support-sync-async].support-asynchronous-process-strategy-flow.stage1.01] org.mule.api.processor.LoggerMessageProcessor: PAYLOAD2
001118386

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.