Celigo provides powerful error-handling features to help you manage and remediate issues efficiently in your Tools. With automated error logging and detailed error messages, you can quickly diagnose and fix problems. You can configure error-handling rules to determine how failures are managed.
For example, errors can originate from connected applications or external systems that your Tool interacts with. A common issue is authentication failure, which can occur when API keys, OAuth tokens, or login credentials are incorrect or have expired.
Network connectivity problems, such as timeouts or service unavailability, can also prevent a successful connection to external platforms. Data mismatches between your Tool input and destination applications—such as unexpected field formats, missing required values, or API schema changes—can also cause failures.
Addressing errors often requires checking API credentials, verifying data formats, and consulting the external system’s documentation for recent updates or limitations.
Use Error handling to choose whether the process should stop and return an error if a record fails or continue to the next step. When one of the lookups or imports encounters an error, you can:
Tip
You can configure additional error handling aside from failed records.
-
Stop and return error: This is the default. The Tool execution will stop for the record, the errors array (including the error code, message, and source) will be sent back to the caller.
-
Proceed to the next application regardless: The Tool execution will continue to the next step; however, the "errors" array needs to be manually mapped in results/response mapping to use that information in downstream steps.