Celigo flow error handling is one of the most overlooked parts of an integration build - and one of the most expensive to ignore. When errors go unmanaged, data stops syncing silently, operations teams spend hours chasing bad records, and the business loses trust in the integration. Getting error handling right from the start is faster and cheaper than retrofitting it after go-live.

What is Celigo flow error handling

Celigo flow error handling is the set of configurations that determine what happens when a record fails during a flow run. That includes how the error is logged, whether the flow retries automatically, who gets notified, and whether the failed record is held for manual review or discarded.

Celigo separates errors into two broad types: flow errors, which affect an entire run, and record-level errors, which affect individual records within a run. Most mid-market teams deal almost exclusively with record-level errors - a single order failing to sync to NetSuite while the rest of the batch processes fine. Understanding that distinction shapes how you configure your error management strategy.

How Celigo flow error handling works

When a record fails, Celigo captures the raw error message from the target or source system and stores it in the Errors tab of the relevant flow. Each error entry shows the failed record data, the error message, the timestamp, and the flow step where the failure occurred. This gives you enough context to resolve the issue without digging through system logs elsewhere.

Celigo also maintains an error queue. Failed records sit in the queue until someone resolves them - either by editing the record data and retrying, or by marking the error as resolved. Errors do not auto-expire unless you configure a retention policy, so queues can grow quickly on high-volume flows if no one is actively monitoring them.

The platform supports automatic retries at the flow level. You can configure a flow to retry failed records up to a set number of times on a defined schedule. This is useful for transient errors like API rate limit responses (HTTP 429) or temporary connectivity failures, but it does nothing for data validation errors that will fail every time without a data fix.

Setting up Celigo flow error handling with Celigo

Celigo's prebuilt Integration Apps - including its NetSuite-Shopify, NetSuite-Salesforce, and NetSuite-Amazon connectors - come with basic error handling preconfigured. But the defaults rarely match what a real business needs. Here is where to focus during setup.

Enable flow alerting immediately. In the flow settings, configure email alerts to fire when a flow encounters any error. Route these to a shared operations inbox, not an individual. Individual-routed alerts get missed during leave or role changes and create blind spots in coverage.

Use retry logic selectively. Set automatic retries only on flows that connect to systems with known rate limits or occasional downtime - for example, flows hitting the Shopify or Amazon APIs. For ERP-bound flows where errors are almost always data quality issues, retries waste compute and obscure the real problem.

Segment your flows by error tolerance. High-volume, low-stakes flows (like product catalog syncs) can tolerate a higher error threshold before alerting. Revenue-critical flows (order creation, invoice sync, payment posting) should alert on the first failure. Celigo lets you set error thresholds per flow - use them.

Build a resolution workflow. Decide in advance who owns error resolution, how long they have to act, and what escalation looks like. Without a defined process, errors accumulate and get resolved inconsistently. Teams working with Entech often pair this with a weekly error review cadence during the first 90 days post-launch.

Timeline and cost

Configuring solid error handling on a new Celigo integration typically adds 4 to 8 hours of implementation work per flow, depending on complexity. For a mid-market business running 5 to 10 flows, that is 20 to 60 hours of setup time - roughly $3,000 to $9,000 at standard consulting rates if you are using a partner like Entech.

The cost of not doing it is harder to quantify but consistently higher. A single undetected sync failure on a high-value order can cost more in customer service and remediation than a full error handling engagement. Teams that skip this step typically spend 2 to 3 times more on reactive troubleshooting in the first six months post-launch.

Common errors and how to fix them

HTTP 429 - Too Many Requests. This happens when your flow sends requests faster than the target API allows. Fix it by enabling rate limiting in the connection settings and configuring automatic retries with exponential backoff. Most Celigo connectors for Shopify and Salesforce have this option built in under the connection's concurrency settings.

Required field missing or null. A record arrives at the destination system without a value in a mandatory field. The fix is upstream - add a filter in Celigo to catch records missing the field before they reach the export step, or add a default value mapping. Retrying this error without fixing the source data will always fail.

Duplicate record detected. NetSuite in particular will reject records that violate unique field constraints - external IDs, transaction numbers, customer IDs. The fastest fix is to check whether a prior run created a partial record and clean it up manually, then confirm your flow's deduplication logic is using the right key field.

Authentication token expired. OAuth tokens on connections like Salesforce or QuickBooks Online expire on a schedule. Celigo surfaces this as a connection error, not a record error, so it takes down the whole flow rather than individual records. Set a calendar reminder to refresh tokens before expiry, or configure Celigo's auto-refresh where supported. Salesforce connected app tokens can be set to non-expiring in the Salesforce org settings.

FAQs

What is the difference between a flow error and a record error in Celigo?
A flow error stops the entire run - usually caused by a connection failure or authentication issue. A record error affects only the specific record that failed while the rest of the batch continues processing. Most day-to-day error handling work involves record-level errors.
Does Celigo automatically retry failed records?
Yes, but only if you configure it to do so. In the flow settings, you can enable automatic retries and set the frequency. This is most useful for transient API errors and not for data validation failures, which require a data fix before retry.
How long does Celigo keep errors in the error queue?
By default, Celigo retains errors based on your subscription plan's data retention policy, which typically ranges from 30 to 90 days. Errors do not auto-resolve - they stay in the queue until manually resolved or retried successfully.
Can Celigo notify Slack or Teams when a flow fails?
Native alerting in Celigo sends email notifications. For Slack or Teams alerts, you can use a webhook-based flow or a monitoring tool like PagerDuty connected via Celigo's HTTP connector. Entech has built this pattern for several clients running 24/7 order pipelines.
Should error handling be set up differently for real-time flows versus scheduled batch flows?
Yes. Real-time flows - like order creation triggers - need immediate alerting because a failure affects a live transaction. Batch flows can tolerate a threshold-based alert, for example notifying only when more than 5% of records in a run fail. Matching alert sensitivity to flow criticality keeps your inbox actionable rather than noisy.

Need help setting up Celigo flow error handling for your integrations? Entech Solutions is a certified Celigo partner - book a free scoping call to walk through your current setup and identify where errors are slipping through.