The Automation Log is a helpful resource to track the success of program and stage automations and can also be helpful in troubleshooting the instances where an automation may have fired unexpectedly. This article is an overview of the Automation Log and includes and overview of the record that is logged as well as how that record can be used to monitor application activity.
The automation log allows you to monitor and troubleshoot active automations within your site. Unlike the Email Logs, the Automation log is unique to and accessible from any program within a site. This means that each program will have its own automation log displaying only records of automations relevant to that program.
The log will consist of a series of timestamped records that are generated whenever an automation fires successfully. By default, the records will be listed in chronological order starting with the most recent record to fire successfully. These records can be useful in many scenarios, such as:
The automation log of a program can be accessed from two places: while editing an automation, or from the Automation tab while viewing a program in build mode.
To access the log while editing an automation:
To access the log from the Automation tab
Records are only generated when an automation fires successfully. If a record isn't appearing and you believe it should have fired, first check that the automation is active. If active, did the activation occur? Next, review the application material against the conditions. For example, does the automation require that ALL conditions be met, or ANY? Also review the matching parameters of the set rules to ensure they have been set correctly. If the automation is active, the activation occurred, and the conditions have been satisfied, Contact Support for assistance.