Update legacy modules with new modules

most {{product name}} apps rely on external services, particularly their apis (application programming interfaces) as services evolve, so do their apis when services release a new api version, their {{product name}} app eventually becomes deprecated and shuts down the result is a legacy (outdated) module in {{product name}} {{product name}} regularly implements new app versions that align with services' latest apis to keep your {{scenario plural lowercase}} running, make sure to update legacy modules to the latest versions here's a step by step guide to updating legacy modules in {{product name}} , using google drive as an example step 1 identify the legacy {{scenario singular lowercase}} a green double arrow icon (below) indicates a legacy module step 2 clone the legacy {{scenario singular lowercase}} clone the {{scenario singular lowercase}} to make a copy you will use this scenario from now on in the {{scenario singular lowercase}} diagram, open the options drop down menu in the top right corner select clone in name of new scenario , name the copied {{scenario singular lowercase}} to enable the {{scenario singular lowercase}} to pick up where its old version left off, select yes in keep the states of any modules the same as those being duplicated click save we recommend opening the legacy {{scenario singular lowercase}} in a new tab to easily compare its configuration settings with those of the new {{scenario singular lowercase}} step 3 access and select new modules in your new (copied) {{scenario singular lowercase}} , choose the legacy module you need to upgrade and click on its green double arrow icon click show me new modules and select the corresponding module the new module will appear in the scenario builder, but remains unconnected in the new modules list, some modules may no longer be available in this case, choose the next best fit step 4 update the trigger module move the clock icon from the legacy module to the new module unlink the legacy module and subsequent module, and link the new module with the desired module set the values of the new module keep in mind that some fields may be different step 5 update other modules update the next legacy module, following the same process outlined in step 3 (access and select new modules) connect the new module to (after) its legacy module set the values of the new module if any items are missing in the mapping panel, see our mapping docid\ upfwozscc5soixr2954z2 documentation repeat this process for any remaining legacy modules step 6 clean up and finalize remove all legacy modules from your new {{scenario singular lowercase}} with right click and delete module click save to save your {{scenario singular lowercase}} you have now updated your legacy modules to their newest versions this process ensures your {{scenario plural lowercase}} continue to run properly as external services evolve their apis