Iconnek documentation
  • Quickstart
    • Introduction
    • Quick start guide
  • Configure
    • Connectors
    • Webhooks
    • Filter Lists
    • Conversion Tables
  • Using iconnek
    • Using the Iconnek Editor
      • Scenarios
      • Nodes
      • Data supervision
        • Dashboard
        • Terminal
        • Context Viewer
    • The Nodes
      • Comment
      • Exception
      • Function
      • Switch
      • Fan Out
      • Sequencer
      • Connector
      • Filter
      • Conversion
      • Mail
      • Catch
    • Using the Function node
    • Working with messages
    • Using global variables
    • Error handling
  • Deploying iconnek
    • Scheduling
    • Deployment
  • Ressources
    • How-to integrates
      • ConnectWise
      • Folks API V2
      • Genius ERP
      • Hector
      • Jovaco
      • Open AI
      • NetSuite
      • Microsoft Dynamics 365 Business Central
      • Zoho Books
      • Zoho CRM
  • Billing
    • Usage
  • PARTNERS
    • Partners
  • Security
    • Security
    • Service Level Agreement
  • Support
    • Contacting Support
Propulsé par GitBook
Sur cette page
  • Types of Errors
  • Error Handling Tools
  • Best Practices
  1. Using iconnek

Error handling

Understanding Error States

When building scenarios in Iconnek, it's essential to plan for both success and failure conditions. The visual indicators on nodes provide immediate feedback on execution status:

  • Green light: Node is executing successfully

  • Red light: Node has encountered an error

Types of Errors

Iconnek provides two distinct ways for nodes to report errors:

Uncatchable Errors

These errors are only written to the log and appear in the Debug sidebar and log output. While visible for debugging purposes, you cannot create flows to handle them automatically.

Catchable Errors

When a node properly notifies the runtime of an error, you can use the Catch node to trigger error-handling flows. These errors can be programmatically managed within your scenarios.

Error Handling Tools

Catch Node

The Catch node is your primary tool for handling errors. When an error occurs, the Catch node receives a message with detailed error information in the msg.payload property. This allows you to create sophisticated error handling logic.

Debugging Tools

Iconnek provides powerful debugging capabilities to help diagnose issues:

  1. Terminal View: Displays real-time execution logs and error messages

  2. Context Viewer: Allows you to examine the data state at different points in your scenario

Best Practices

When designing robust scenarios, consider:

  • What happens if external services (databases, APIs) become unresponsive?

  • Do you need retry logic for failed operations?

  • Should errors trigger alerts or notifications?

  • Are some errors actually expected events that need specific handling?

Remember that proper error handling is essential for creating reliable, production-ready integration scenarios that can gracefully manage unexpected situations.

PrécédentUsing global variablesSuivantScheduling

Dernière mise à jour il y a 3 mois