You can duplicate an automation from the automations listing page. A copy of the existing automation and all the current configurations is created, i.e., trigger(s) and action(s). Since the original and the cloned automation are in the same project, they can share important attributes, such as invited users and connected apps.
Creating a duplicate version of an automation can be useful for a number of reasons:
To clone an automation, perform the steps given below:

Note: You can now throttle the execution for your automations to avoid rate limit. For more information, refer to the Throttle Execution document.
If the automation is cloned in the same project, some steps may appear as tested and untested. If any action has a dependency on the previous step and that step remains untested, then all the subsequent steps become untested.
You can find the dependency by checking the automation step number in the active action step. If the current step fetches value from the untested step, it becomes dependent on the previous step to testify as tested.
Note: If a user clones an automation to a different project, all the automation steps become untested and the user needs to configure connected apps to activate the automation.
If you have defined project variables in your project and used them in your automation, then you can copy the project variables to the destination project for the cloned automation to work properly.
Note: Project Variables are defined at project level.

