Error classifications

When you view the list of errors encountered in a flow, each open and resolved error is labeled according to its type, or “classification.” Errors are categorized according to their properties, such as the code, message, and source fields.

The Classification column helps you quickly recognize and filter errors, even when the escaped JSON or third-party app error messages are difficult to read.

Then, in the detailed view per error, the classification appears above the trace key.

Errors are automatically placed into one of the following read-only classifications; the value is blank if none of them applies. Contact support if the classification appears to be incorrect. (After checking the typical causes provided below for troubleshooting, see also Investigate errors and Retry or resolve errors.)

Classifications

• Value
• Missing
• Connection
• Intermittent
• Rate limit
• Too large
• Parse
• Duplicate

While you might still notice Governance temporarily listed in the Classification, from the 2023.9.1 release onwards, Governance errors will be reclassified as Rate limit or Too large errors. When you now run any flows, you will see rate limit or too large errors, instead of governance errors. In previous flow runs, if you had governance errors you can still view or edit them. When you now retry them or run the flow, they will show either as rate limit or too large. This reclassification does not affect the errors in any way, it is a renaming to better identify the errors and fix them.

Value

Missing

Connection

Intermittent

Rate limit

Too large

Parse

Duplicate

Blank value

The error cannot be classified with high confidence, despite the millions of integration and API errors and artificial intelligence at Celigo’s disposal. However, such occurrences are regularly reviewed for additional classification.