Workflow logs are where we help you track each and every Workflow and its outcomes through Fyno’s App for you.
Workflow logs are a detailed view of what has happened on each of your Workflow, with vital information for you to further analyse and derive conclusions about your Workflow , and to further improve your communication strategies.
When we go to the “Workflow Logs” from the left navigation menu, we see the following sections:
The logs that are seen on the “Workflow Logs” page give you an overview of the latest activity that has occurred on your Workflow
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:
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.
Displays the time that the Workflow triggered was initiated
Displays the name of the Workflow that has been triggered
Displays the total no of actions that are successful. For example, if your workflow has 3 notification events configured and only 2 of them got sent successfully, then you will se 2 out of 3 successful.
Displays the Trigger Type of the input that triggered the Workflow. This can be:
Display the source IP from which this Workflow trigger was initiated from.
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 Workflow that have been generated.
Filters within the Workflow logs page help you seamlessly sift through all the logs that have been generated for all the Workflow that have been triggered through the Fyno App.
To understand how to use the filters, let’s have a look at the categories within filters.
“Date Range” allows you to specify the time frame for which you want to view the logs.
You can select one of the provided options, which are:
The “Request ID” option allows you to look for Request IDs, which you would have received for a notification within an Workflow. This is crucial to do individual debugging and trace a notification
The “Custom Name” option allows for you to look for any Workflow logs based on the name. This can be a partial search or an exact match search too.
The “Request ID” option allows you to look for Workflow IDs, which you would have received for an Workflow. This is crucial for debugging and tracing an issue at an Workflow level. This would give you multiple records, based on the common Workflow ID
Select the input Trigger Type of the Workflow. This can be:
You can select the “Status of your Workflow as a filter to narrow down your search. The statuses that you can choose from are:
For Workflow (with trigger types - Webhook, Virtual No or Mixpanel)
For Journey (with trigger type - Notification Event)
This filter is particularly helpful when you want to have a bird’s eye view of only failed statuses to help debug and solve them.
Workflow logs cover a descriptive log of each step of the Workflow, and what has happened. Let’s take a closer look at the Workflow logs and what exactly each aspect of the logs talks about.
You can easily have a look at the “Workflow Details” by simply clicking on the Workflow log when you see it on the “Workflow Logs” Panel.
When the log details open up, the first thing you will see on the left is the trace log for the Workflow.
This gives you a bird’s eye view of the entire Workflow, the path it has taken and what has happened at every step.
Depending on what elements are used for your Workflow configuration, you will see the following: