This pattern uses the AQ_StartProject service in 'Start without user interface' mode to call a flow in a project that can be located in a completely different repository. The call of the flow is straightforward, whereas receiving the answer is more difficult. The AQ_StartProject service does not set any output itself, as it just starts a function in a different repository. It is therefore an appropriate decoupling pattern if no output is needed from the other flow (fire & forget).
It is not adviced to use this pattern when an answer is needed. Solutions such as the AQ_Aggregate_Read service are difficult to make resilient. One problem is that the execution is in parallel, you can not be sure that the information is already up-to-date. Such a workaround also worsens the characteristics of this pattern.
Characteristics
Unable to render {include} The included page could not be found.
Overview
Content Tools