What happens if the reference value does not match?

Data integrity is paramount in cross-sheet automation. When Trigger Flow detects a change in your source sheet but cannot find a corresponding row in the destination (based on the Reference Column), it follows a Safe-Fail Protocol designed to protect your data.

What Happens During a Mismatch

1. No Data is Written: The destination sheet is not modified. No "ghost rows" are created at the bottom of your sheet.
2. Event is Logged: The mismatch is recorded in your SmartSyncApp dashboard with the source row ID, the reference value that failed to match, and a timestamp.
3. Flow Continues: The mismatch does not block subsequent sync events. If the next change has a valid match, it will sync normally.

Common Causes of Reference Mismatches

In our experience supporting enterprise deployments, the most frequent causes are:

• Whitespace Discrepancies: A leading or trailing space in "PROJ-001 " vs. "PROJ-001" will cause a silent mismatch. Use Smartsheet's TRIM() formula to clean reference columns.
• Case Sensitivity: Reference matching is case-sensitive. "proj-001" will not match "PROJ-001".
• Archived or Deleted Rows: If the destination row has been moved to another sheet or deleted, the reference value no longer exists in the target.
• New Source Records: If a new row is added to the source sheet before it has been added to the destination, the first sync will mismatch until the destination is populated.

Expert Resolution Strategy

We recommend a weekly "Data Drift Audit" for mission-critical flows. Export your mismatch log from the SmartSyncApp dashboard and cross-reference it against your source and destination sheets to identify systematic alignment issues before they compound.