Data is not syncing

Start by checking whether the issue is global or limited to your workspace.

• Open the ACEIRT™ Fusion status page or in-product banner if one is shown.
• Look for any incidents related to syncs, connectors, or background jobs.
• If there is an ongoing incident, wait for the status to return to operational, then verify whether your data has caught up.

If the service is operational and other users do not report issues, continue to the next step.

Make sure ACEIRT™ Fusion still has a valid, authorized connection to your data source.

• Go to your ACEIRT™ Fusion integrations or connections page.
• Locate the affected data source and check its connection status.
• If the connector shows disconnected, expired, or needs re‑authorization, reconnect it.
• Re-enter any required API keys, tokens, or passwords if they have changed or expired.

After updating credentials, save the connection and confirm it shows as connected before moving on.

Even if the connector is active, the underlying account might not have permission to read all required data.

• Identify which account or API key ACEIRT™ Fusion uses for the sync.
• In your source system, review that account's role and permissions.
• Confirm it has read access to the records, objects, lists, or folders you expect to sync.
• If permissions were recently tightened, restore read access or create a dedicated integration user with stable access.

Once you update permissions, trigger a manual sync (if available) and watch for new records appearing.

If some data syncs but specific records or fields are missing, your sync configuration may exclude them.

• Open the configuration for the affected integration in ACEIRT™ Fusion.
• Check any filters, segments, or query conditions that define which records sync.
• Confirm that the missing records match the filter criteria; adjust filters if the scope is too narrow.
• Review field mappings and ensure critical fields are mapped to the correct ACEIRT™ Fusion fields.
• Make sure required fields in ACEIRT™ Fusion are not mapped from empty or deprecated fields in the source.

Save your configuration changes and note the time so you can verify when new data arrives.

Some data sources enforce limits that can delay or block syncs.

• Check any sync logs or activity views in ACEIRT™ Fusion for messages about rate limits or throttling.
• In your source system, review API dashboards or logs for signs of too many requests from ACEIRT™ Fusion.
• If you see rate limit errors, reduce sync frequency, narrow filters, or schedule syncs during off-peak hours.

When rate limiting is the cause, syncs may complete slowly rather than fail entirely. Expect data to catch up after the limit window resets.

After fixing connection, permissions, and configuration, run another sync and confirm it succeeds.

• From the integration settings in ACEIRT™ Fusion, start a manual sync for the affected data source.
• Monitor the sync progress or logs until it finishes.
• In your ACEIRT™ Fusion workspace, open a record that was previously missing and confirm it now appears with the latest data.
• Compare the last updated timestamp in ACEIRT™ Fusion against the source system to ensure they are close in time.

If data still does not sync after a successful run, move to the support steps.

If this is a new integration and data has never synced successfully, revisit the original setup.

• Follow the connection steps in the setup guide: Connect a data source.
• Confirm you selected the correct environment (for example, production vs sandbox) in both ACEIRT™ Fusion and the source.
• Ensure you completed any required setup inside the source system, such as enabling API access or installing an app/extension.

Once setup is complete, trigger another sync and check whether the first batch of data appears.

If you still see missing or outdated data after completing the previous steps, contact ACEIRT™ Fusion support so the team can investigate.

Include the following details in your ticket to speed up resolution:

• Your workspace or account name.
• The data source that is not syncing and the specific objects or records affected.
• Whether syncs previously worked, and if so, when they last worked as expected.
• A few concrete record examples (IDs or URLs) that should sync but do not.
• Screenshots or exports from your source system showing the expected data.
• Any error messages or log entries from ACEIRT™ Fusion related to the sync.

With this information, support can trace the sync, check backend logs, and advise on next steps or fixes.