WEBVTT

00:00.960 --> 00:07.160
In this lesson, we are going to learn how to use the executions log to monitor, debug and troubleshoot

00:07.160 --> 00:08.560
your workflows in N810.

00:09.240 --> 00:14.360
N810 is amazing because it allows you to track every execution of your automation.

00:14.800 --> 00:19.920
This means you can see exactly what happened when errors occurred and what needs to be fixed.

00:20.080 --> 00:23.240
Let's use feedback collection form automation.

00:23.240 --> 00:28.480
So when building automation or AI agents you can see that right here.

00:28.960 --> 00:31.880
We can switch between editor and executions.

00:36.480 --> 00:40.120
So the editor is where we build workflows and executions.

00:40.120 --> 00:45.080
Log is where we check if the workflow ran correctly or if there were any issues.

00:46.400 --> 00:51.040
So you can simply switch to execution tab and see a list of executions.

00:51.680 --> 00:54.720
So each execution has a status color.

00:55.320 --> 01:03.080
So green means workflow runs successfully and red means workflow failed.

01:03.360 --> 01:04.840
So you need to check for errors.

01:05.280 --> 01:10.380
You can also see the exact date and time each workflow was executed.

01:11.980 --> 01:19.820
So when you click on any execution to view details, this opens a breakdown of workflow run.

01:20.620 --> 01:27.660
So you can see which nodes executed successfully and in which nodes an error occurred.

01:27.660 --> 01:32.860
In that case, our workflow executed successfully so there are no errors.

01:33.140 --> 01:36.940
But when we check our previous, uh, automation.

01:38.220 --> 01:39.660
So let's click on this one.

01:47.580 --> 01:50.820
You can see that there is an error in a Google Sheets node.

01:55.700 --> 02:00.300
So if if a node failed click on it to read the error message.

02:01.100 --> 02:07.300
And this will tell you what went wrong for example missing API key, wrong data format, etc..

02:10.420 --> 02:15.730
So in that case at least one value has to be added on the values to send.

02:16.210 --> 02:27.010
Because in this specific run of this automation, I have not included a variables into these fields.

02:30.850 --> 02:33.570
Now you cannot edit anything in the executions log.

02:33.610 --> 02:41.010
It's only for checking past runs, so I can't just drag and drop these values into those fields.

02:44.490 --> 02:52.370
If you find an issue and you face some errors, you need to switch back to the editor and fix it in

02:52.370 --> 02:53.090
your workflow.

02:55.850 --> 02:57.450
So let's go back to our editor.

03:00.970 --> 03:02.090
So to conclude.

03:04.250 --> 03:11.850
You should use Executions Log to help you track workflow history to make troubleshooting easier and

03:11.850 --> 03:14.610
to let you test workflows step by step.

03:14.970 --> 03:19.930
So always check the execution log if you get errors or need to debug your workflows.