Use scenario outputs

once you define your {{scenario singular lowercase}} outputs, you need to add the dedicated scenarios > return output module the return output module has module fields based on {{scenario singular lowercase}} outputs setting map the data you want to output from your {{scenario singular lowercase}} to the return output module fields {{product name}} is not billing you for operations used by the return output module you can use {{scenario singular lowercase}} outputs as much as you like the return output module always finishes the {{scenario singular lowercase}} run it works similarly as the return statement in programming you cannot add any subsequent modules after the return output module in the current route keep in mind that when using routers, a return output module in a route finishes the {{scenario singular lowercase}} the modules in the subsequent routes won't run if you have multiple return output modules in your {{scenario singular lowercase}} , {{product name}} runs only the one that is reached first in the {{scenario singular lowercase}} flow subsequent return output modules don't run {{scenario singular}} outputs are available to the entity that triggered the {{scenario singular lowercase}} if the {{scenario singular lowercase}} was triggered through the call a subscenario module, then {{scenario singular lowercase}} outputs are a part of the module output bundles if the {{scenario singular lowercase}} was triggered through the make api, then {{scenario singular lowercase}} outputs are in the request response