Scenario execution flow

in this section, you will learn how a {{scenario singular lowercase}} executes and how data flows through a {{scenario singular lowercase}} it will also show you where you can find information about your processed data and how to read it once a {{scenario singular lowercase}} is set up docid 4inplgaxo0copid3px2ys correctly and active and inactive scenarios docid\ pdrftysejpiiztab7zjyh , it will execute according to its defined schedule docid\ scpfttwgfapf077ujo1jh the {{scenario singular lowercase}} begins with the first module docid\ pdopibceckcbomppkplmy responding to an event it has been set to watch for if it returns any bundles (data), the bundles are then passed on to the next module and the {{scenario singular lowercase}} continues if it does not return any bundles, the scenario does not continue and ends after the first module in the case where there are returned bundles after the first module, the bundles will then go through each proceeding module one by one if the bundles are processed correctly throughout all of the modules, the {{scenario singular lowercase}} is then marked as successful example connecting facebook to dropbox the example below shows how make connects three modules in a {{scenario singular lowercase}} it explains how make downloads photos from facebook docid\ xragcghcpyj0o9gcxgyu8 , converts them to another format, and sends them to a selected dropbox docid 3cpjivvixwccbveensaam folder when the {{scenario singular lowercase}} begins, the first step is to watch for bundles in this case, it is to watch for photos on facebook if it does not return a bundle (a photo), the processing of the {{scenario singular lowercase}} does not continue and ends after the first module if a bundle is returned, the bundle then passes through the rest of the {{scenario singular lowercase}} the bundle is first recieved through the watch photos module, then it goes through the convert a format module for the image app, and then goes through the upload a file module for dropbox to reach its final destination, the dropbox folder it is also important to note that if facebook returns multiple bundles, for example two bundles, the processing of the latter bundle will not start until the first bundle is converted and uploaded to dropbox information about processed bundles for each module, the bundle goes through a 4 step process before going on to the next module or reaching its final destination the 4 step process is initalization, operation, commit/rollback, and finalization this is called transaction processing and it helps to explain how data was processed in a module once a {{scenario singular lowercase}} run is complete, each module displays an icon showing the number of operations performed clicking this icon will display the detailed information about the processed bundles, in the format described above you can see which module settings docid\ vnbss belmdin3d4gguxl were used and which bundles were returned by which module the picture above illustrates the processing of the last module used in the {{scenario singular lowercase}} above, the dropbox module, upload a file the module received the following input information converted image selected folder where the image shall be uploaded to original name of the facebook image after processing, the module returned this output information image id assigned by dropbox full path where in dropbox make uploaded the file the above information is captured for each bundle separately, as marked by the drop down boxes operation 1 and operation 2 in the image errors while executing a {{scenario singular lowercase}} an error may occur during the {{scenario singular lowercase}} run for example, if you delete the dropbox folder that you have set as the target folder in the module setting, the {{scenario singular lowercase}} will terminate with an error message for more information on this and to learn how to handle errors, please see the error handling docid w3dqogjxm4xl3s64h40 help guide