A Celigo integration not syncing is almost always one of four problems: an expired connection, a broken field mapping, a paused or errored flow, or an API rate limit from NetSuite, Shopify, or Salesforce. Each one leaves a different signature in the Celigo integrator.io dashboard, and most take under 15 minutes to diagnose once you know where to look. This guide covers the diagnostic steps and fixes Entech Solutions uses across the 200+ Celigo integrations we've supported.
What causes a Celigo integration to stop syncing
Celigo integrator.io moves data between systems through "flows" - scheduled or real-time jobs that pull records from a source system and push them to a target. When a flow fails, records queue up in an error log instead of disappearing silently. In most cases the integration isn't broken - it's paused, throttled, or blocked on a specific record.
The most common root causes are credential expiration (OAuth tokens or NetSuite Token-Based Authentication expiring), schema drift (a custom field gets renamed or deleted in NetSuite or Salesforce without updating the mapping), and volume spikes that trigger API rate limits on the connected system.
How Celigo flows sync data between systems
Each flow has three parts: a trigger, an export, and an import. The trigger fires on a schedule - every 5, 15, or 60 minutes - or in real time via webhook, for example a new Shopify order or a NetSuite inventory change. The export pulls matching records, and the import writes them into the target system field by field, based on the mapping configured during setup.
Bidirectional flows, like customer sync between NetSuite and Salesforce, run as two separate one-way flows with independent error handling. If one direction fails, the other keeps running, which is why data can look current in one system and stale in the other.
Fixing a Celigo integration that's not syncing
Start in the Celigo dashboard, not in NetSuite or Shopify.
- Open the flow showing an error badge and check Run History for the exact error message and timestamp.
- Check Connections - a red or yellow indicator means the OAuth token or NetSuite RESTlet credentials need re-authentication.
- Review the Error Management queue for the specific records that failed. Celigo shows the field-level error, not just a generic failure.
- Fix the root cause - remap the field, refresh the token, adjust the schedule - then retry the queued records instead of waiting for the next scheduled run.
If you're running Celigo's prebuilt connectors, like the NetSuite-Shopify Connector or NetSuite-Salesforce Connector, check the release notes first. Celigo updates these templates periodically, and an outdated version can break after a source API deprecation.
Timeline and cost to fix sync issues
Most sync failures resolve same-day - typically 1-3 hours once someone with Celigo admin access is looking at it. Recurring issues from schema drift take longer, usually 1-2 days, since they require coordinating a mapping update with whoever changed the source system.
Paying an agency to fix a one-off issue runs $150-250/hour. Ongoing Celigo maintenance retainers with monitoring and proactive error handling run $1,000-3,000/month. Businesses running 5+ flows across NetSuite, Shopify, and Salesforce usually find the retainer cheaper than paying hourly every time something breaks.
Common Celigo sync errors and how to fix them
These four account for most support tickets on active Celigo integrations:
- "Invalid Login Attempt" or 401 errors: NetSuite Token-Based Authentication or a Shopify Admin API token expired. Regenerate the credential in the source system and re-enter it under Celigo Connections - this also happens if the dedicated integration user gets deactivated by mistake.
- "Field not found" or undefined mapping errors: a custom field was renamed or deleted after the flow was built. Open the field mapping screen, remove the broken reference, and remap to the current field.
- API rate limit errors: a batch flow is pulling too many records too fast for the source system's concurrency limits. Reduce the batch size or shift the schedule to run less frequently during peak hours.
- Duplicate record creation: the flow is matching on the wrong unique identifier, like email instead of internal ID. Update the lookup criteria in the import step so Celigo checks for an existing record before creating a new one.
FAQs
- Why did my Celigo integration stop syncing overnight?
- Usually a token expiration or a maintenance window on the connected system, like NetSuite or Shopify. Check the connection status in Celigo first - a red indicator means re-authentication is needed before any flow will run.
- How do I know which records failed to sync?
- Open the flow and check Error Management, which lists every failed record with its specific error message. This is more useful than checking the source or target system directly since it shows exactly why Celigo rejected the record.
- Can I fix sync errors without technical help?
- Re-authenticating a connection or retrying queued records can be done by anyone with Celigo admin access. Field mapping errors and schema changes usually need someone who understands both the source data model and the flow configuration.
- Does Celigo alert me automatically when a sync fails?
- Only if configured - Celigo supports email and Slack notifications for flow errors, but they're not enabled by default. Set these up during initial configuration so failures get caught within minutes, not days.
- Will Celigo's prebuilt connector prevent future sync issues?
- It reduces them but doesn't eliminate them - prebuilt connectors still break when custom fields change or APIs get deprecated. They do get maintained and updated by Celigo, which custom-built flows don't.
Need help fixing a Celigo integration that's not syncing? Entech Solutions is a certified Celigo partner - book a free scoping call.