7. Error handling
Error workflows are essential for effectively managing and debugging workflow errors.
Understanding n8n's workflow execution and error handling
•
📊 In this video, we looked at how past executions are stored in n8n and the importance of effectively managing workflow errors .
•
🔍 Most of the executions we've done have been done manually, but once a workflow is activated , it runs automatically and you can access the execution history via the execution log .
•
🗂 The execution log shows both successful and failed executions , and manual executions are not saved by default, but can be logged per workflow .
•
⚠ It is important to understand how to handle these errors, as they can occur for a variety of reasons, including incorrect settings during execution or improperly formatted input data **.
•
🛠 One of the main ways to manage errors is to leverage error workflows, which are activated when a node error occurs and provide essential information needed for debugging.
•
📩 We recommend setting up a communication channel like Slack or Teams to receive error reports so your team can address issues promptly .
•
🔗 We also demonstrated how to create a simple error workflow that sends a notification about an error, including details like the workflow name and an easily accessible execution URL .
•
🔄 In the next video, we'll look at debugging techniques to prevent future errors and explore the retry mechanism in your workflow .
LiveWiki, the key content on YouTube in 10 seconds! - https://livewiki.com/ko/content/n8n-beginner-course-error-handling
In this video, we will cover how to save the execution history of a workflow and how to handle errors.
•
Execution history can be checked in the Execution Log .
•
Successful and failed execution records of activated workflows are stored.
•
Manual runs are not saved by default, but can be saved via settings.
•
You can check the status of each node through the execution log and get help with debugging.
•
You can check the input, output data, and error details of each node.
•
Explains how to identify and fix the cause of a workflow error.
•
Workflows can fail due to setup errors or input data format errors.
•
Error Workflow Description: A workflow that is automatically executed when an error occurs.
•
Helps with reporting errors and fixing workflows.
•
Example of an Error Workflow: Reading data from a Google Sheet, and throwing an error in a Salesforce node due to an entry not containing an email.
•
Error Workflow is executed with information about the node where the error occurred.
•
Stop and Error node : Generates an error message and stops the workflow under certain conditions.
•
Available for edge case handling.
•
Report error information using the Error Trigger node in the Error Workflow .
•
You can set up a message to notify you of errors via Slack, email, or Telegram when an error occurs.
•
07:06 – 08:34:
◦
Example of building a simple Error Workflow: Send error information as a Slack message when an error occurs.
◦
Set up Slack notifications, including workflow name, execution URL, error messages, and more.
•
08:34 – 09:39:
◦
Explains how to test Slack messages and send error notifications to channels.
◦
Ability to quickly share error information with multiple users.
•
09:39 – 11:53:
◦
Add error handling methods to existing workflows.
◦
Generate error messages using the Stop and Error node when errors occur in email validation and event type validation .
•
11:53 – 13:47:
◦
Use the Stop and Error node to handle errors when the email is invalid or there are no events.
◦
Set error messages for each error condition to help debug your workflow.
•
13:47 – 14:32:
◦
You can decide whether to continue execution after stopping the workflow in the Stop and Error node settings.
◦
In edge cases, you can configure the workflow to continue even after an error occurs.
•
14:32 – 15:12:
◦
This video covers execution history management, error handling, and building a basic Error Workflow.
◦
In the next video, we'll cover how to debug your workflow and retry errors.