Learn how to troubleshoot some of the most common issues that come up while using DataMesh.
Troubleshooting DataMesh
| Behavior | Cause | Resolution |
|---|---|---|
| Blank rows are added to my sheet. | The rows previously had information in them, but the cell information was deleted. Cells retain the history of their previous contents, so it's possible that DataMesh treats them as though they have information. | Delete the entire row using the row menu. |
| DataMesh periodically fails to run when set to update immediately. | DataMesh will periodically fail to run when set to Update Immediately. If the DataMesh servers have a large queue of jobs to process, or the config otherwise fails to run immediately, the config will default to 1-hour update frequency. | If the config misses its immediate update, it will be set to process in the next hourly update frequency for the next run. The config UI will continue to display update. No changes are required. |
| Some or all mapped fields don't copy into the target sheet for some or all rows/columns. | A target column is restricted to certain values or data-types, by the source column has a value which doesn't meet the restriction. A target column is restricted to certain values or data types but the config is set to create cell links. A target column is a system column. A Predecessors column is mapped. | Remove or correct the invalid data values in the Source sheet. Edit column properties of target columns and set to non-data strict (Dates, Contacts, Checkboxes, or Dropdowns). Verify that no System column is targeted and remove if needed. Verify that no Predecessors column is mapped and remove if needed. |
| DataMesh is not updating data in the destination sheet. | The underlying sheet has changed. Typically the column names in the Source or Target sheet were changed (changing the column type will not require an update to the config). | The config needs to be updated to account for the new sheet changes. |