Automation Logs

Automation logs are where we help you track each and every Automation and its outcomes through Fyno's App for you.

Automation logs are a detailed view of what has happened on each of your Automations, with vital information for you to further analyse and derive conclusions about your automation flow, and to further improve your communication strategies.

This section covers the Automation logs that you can see on the Fyno platform, how you can filter through this to narrow down your search and a detailed understanding of the individual logs.

When we go to the "Automation Logs" from the left navigation menu, we see the following sections:

1. Automation Logs
2. Test & Live Versions
3. Filters (explained in next section).

Automation Logs

The logs that are seen on the "Automation Logs" page give you an overview of the latest activity that has occurred on your Automations

When you have a look at the logs, what you will initially notice is the status icon that gives you an overall understanding of if the notification is:

1. Delivered
2. Error
3. Failed
4. Timed out
5. Dropped

This is important for you to understand the status of attempts, especially when you are setting up or configuring the Automation.

To further understand this page, let's have a look at what exactly each column means and the data they contain.

Start Time

Displays the time that the Automation triggered was initiated

Name

Displays the name of the Automation that has been triggered

Total Time Taken

Displays the total time taken for the execution of the Automation as a whole.

Source

Displays the Source Type of the input that triggered the Automation. This can be:

1. API
2. Webhook

Source IP

Display the source IP from which this Automation trigger was initiated from.

Test & Live Versions

In the logs section, the Test and Live versions are uniquely partitioned, in order to show you the details notifications sent in that particular version of the Automations that have been generated.

🚧

Can't find an Automation log?

Check the environment that the Automation was triggered in. Automations triggered in Test environment cannot be seen in Live and vice versa.