Managing Automations

After an Automation is built, you enable and disable it, change its name, description, and Retry Handling, clone it, delete it, and, after a change to its graph that you need to reverse, return to an earlier graph. Returning to an earlier graph is the only one of these that changes the graph, so it is the only one that creates a new Revision. The Automation's name, its description, and its Retry Handling are not part of the graph.

Enabling and Disabling

Allow Automation to Run sets whether the Automation is enabled when you create it, and you can enable or disable it afterwards. A disabled Automation's trigger does not start runs. Disable an Automation to stop it from starting runs without deleting it, for example while a partner's system is being replaced. An Automation created by conversion is disabled until you enable it, as described in Migrating Automations v1 to v2.

Cloning

Cloning an Automation creates a new Automation with the same trigger and nodes. Use it to build a second Automation that differs from the first in one destination or one partner, so that the shared part is not rebuilt node by node.

Deleting

Deleting an Automation removes it and stops it from starting runs. A deleted Automation cannot be restored, so disable an Automation you might need again instead of deleting it.

Returning to an Earlier Graph

To return to an earlier graph, apply its JSON definition in the Builder and save, which creates a new Revision with the earlier graph. Files.com does not store earlier Revisions for retrieval, so keep a copy of a definition you may want to return to, with Copy JSON, before you change it.