Use scenario outputs

once you define your {{scenario singular lowercase}} outputs, you need to add the dedicated scenarios > return output module its module fields are based on {{scenario singular lowercase}} outputs setting map the data you want to output from your {{scenario singular lowercase}} to the scenarios > return output module fields the scenarios > 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 scenarios > return output module in the current route keep in mind that when using routers, the scenarios > return output module in a route finishes the {{scenario singular lowercase}} the modules in the subsequent routes won't run if you have multiple scenarios > 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 scenarios > call a scenario 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