Data isn't syncing correctly

If your workflow is running but data isn't arriving in the destination app as expected — wrong values, missing records, or nothing written at all — this article walks you through the most common causes and how to fix each one.

What you might be experiencing

Your workflow shows as active and runs appear in Workflows → Activities, but something is off in the destination app: records aren't being created, fields are populated with the wrong data, fewer records are syncing than expected, or the same records keep syncing repeatedly. The workflow isn't failing, but it just isn't doing what you intended.

Start here: check the execution log

Before working through the causes below, open the execution log for a recent run. It's the fastest way to see exactly where in the workflow data stopped flowing correctly.

Go to Workflows → Activities in the sidebar.
Find a recent run of the affected workflow and click the magnifying glass icon on that row.
In the execution log, look at the step cards for your trigger and action steps. Each card has three tabs: Status, Data In, and Data Out.

Use these counts to orient yourself before reading further:

Trigger Data Out = 0: the trigger ran but found no records to process. Your data isn't entering the workflow at all. Start with Cause 1.
Trigger Data Out > 0, action Data Out = 0: data entered the workflow but nothing was written to the destination app. Start with Cause 2 or Cause 3.
Action Data Out > 0 but values are wrong in the destination app: data is being written, but the wrong fields are mapped. Go to Cause 3.
Action Data Out = 0 and the action step shows a red ×: the action step failed. Check the Status tab on the action card for the error message, then see How to read workflow error messages.
Records are syncing repeatedly: deduplication may be turned off. Go to Cause 5.

Possible causes

Cause 1: The trigger isn't finding new records

The workflow is running on schedule, but the trigger step is retrieving no data — so there's nothing to pass to the action step.

How this appears in the execution log: Trigger step Data Out = 0.

Common reasons this happens:

There are no new records matching the trigger event since the last run. This would be expected behavior.
The trigger's Start Date (configured in the Settings tab) is set to a date in the future, so Conduitly is looking for records that don't exist yet.
The trigger app's data hasn't changed since the workflow was published. Remember: triggers don't process events that occurred before the workflow was published. Only new events from that point forward are picked up.

How to fix it: Open the workflow, click the trigger node, and navigate to the Settings tab. Review the Start Date field if one is configured and confirm it's set to the correct date. Then check your trigger app directly and confirm that new records matching the trigger event have actually been created since the workflow went live.

Cause 2: A filter is blocking the workflow

If you've configured a filter on your trigger, the workflow only runs when incoming data meets the conditions you defined. If none of your recent trigger records match those conditions, the action step never executes, and nothing is written to the destination app. The workflow is working as configured; the filter is just more restrictive than intended.

How this appears in the execution log: Trigger Data Out > 0, but action Data Out = 0 and the action step may show as skipped or not executed.

How to fix it: Open the workflow, click the trigger node, and navigate to the Test tab. Click the filter icon to open the Filter Setup & Testing modal. Review each condition row and confirm that your recent trigger data actually satisfies the conditions you've set. If the conditions are too narrow, update them and click Save & Apply.

Cause 3: Field mapping is incorrect or incomplete

The workflow is running and writing records to the destination app, but the values in the destination are wrong, blank, or mismatched. This is a mapping configuration issue. The wrong source fields are connected to the destination fields, or required fields were left unmapped.

How this appears in the execution log: Action Data Out > 0, but inspection of the destination app reveals incorrect or missing values.

How to fix it:

Open the workflow and click the action node.
Navigate to the Mapping tab.
Review each mapped field. The source data token shown in each field tells you which trigger field is being sent there. If it's wrong, click the blue + button to open the Choose Data picker and select the correct field.
Use the orange sample values in the Choose Data picker to confirm you're selecting the right field. They show real data pulled from your trigger app during the test step.
Check that all required fields (marked with a red asterisk) are mapped. Blank required fields in the destination app are a common cause of missing or incomplete records.
Once you've corrected the mapping, click Complete ✓ and republish the workflow.

Note: Fixing a mapping only affects future workflow runs. Records already written with incorrect data will need to be corrected manually in the destination app.

Cause 4: The wrong resource is selected in the action

The workflow is writing data to the destination app, but it's going to the wrong place (i.e., the wrong spreadsheet, worksheet, or record type). This is likely a field mapping issue in the action Mapping tab.

How this appears: Records appear in the destination app, but in the wrong location (wrong sheet, wrong table, wrong project, etc.).

How to fix it: Open the action node, navigate to the Mapping tab, and review the first sub-step (resource selection). Confirm that the correct target resource is selected. For example, the right spreadsheet and worksheet if your action app is Google Sheets, or the right record type if it's a CRM. Update the selection if needed and republish.

Cause 5: Deduplication is disabled

If the same records are syncing to the destination app on every run, potentially creating duplicates, deduplication is likely turned off. When deduplication is disabled, Conduitly may process the same records repeatedly rather than only picking up new ones depending on how the integrations send data to us.

How to fix it: Open the action node and navigate to the Setup tab. Find the Deduplication toggle and enable it. Once enabled, the action will only process new data and discard records that have already been synced.

Note: Deduplication is disabled by default.

Cause 6: Sample data from the test run was written to the destination app

If unexpected records appeared in the destination app shortly after you set up and tested the workflow, they may have been created during the action test step in the workflow builder. Testing the action step using the Live test option runs it against real data from the trigger, which means a real record is created in the destination app.

How to fix it: These records can be deleted directly from the destination app. They won't recur. The test step only runs when you manually trigger it during setup. Future automatic runs will only process live trigger events.

Still not working?

If none of the above resolves the issue, contact our support team via the Help button in the bottom-right corner of any page. Include your workflow name and a screenshot of the execution log from Workflows → Activities — specifically the Data In and Data Out counts for each step. This helps us diagnose the problem faster.