Merge and Monday Not Working as Expected...HELP

Questions
1

I am trying to pull data from a table and; update columns on duplicate rows, add new items and data on new rows.

The issue I am having is, this isn’t working. For my Merge nodes, it is based on a single column called Import Column. My table had these values:
O742540203
O742500401
O742457602
O742366701
O742211401
O742098702
O741893201
O741893202
O741880701
O740932102
O740478101

The existing Monday board data had these values:
O743007301
O742982108
O742892802
O742892804
O742777301
O742540203
O742500401
O742211401
O742098702
O741880701
O740932102
O740478101

As you can see, they should have all matched, yet the first Merge node only had 7 output bundles and the second had 9…

Then, the Monday board only updated one existing item and the rest were added as new and the old (duplicate) rows were all deleted.

Whenever I TEST this flow it works fine, it matches duplicate data and overwrites the appropriate cells in Monday, then adds new rows, then deletes any rows that weren’t in the trigger table.

But running live it either does things out of order or is glitching. I don’t know what is wrong or how to fix it.

Information on your n8n setup

  • n8n version: 1.54.4
  • Database (default: SQLite): MySQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Windows 11
3

Hey @anthony.lee_hah , I suspect the issue is due to references to the field like column_values[15].text as this might have produced not what you expect.

To help you out, could you please, provide a sample of the output data produced by MySQL and the first Monday.com nodes. I suspect that before merging you might need modify those values first (most likely for the latter node to avoid using references like column_values[15].text ) so that the Merge node could handle them properly.

Generally speaking, ideally you would provide the name of the field (property) without engaging arrays like column_values[15]. That is why I believe the data needs reformatting before feeding it to Merge node.

4

As it turns out, this was happening because when you update a row in Monday with the same information that it already had, the last_updated pulse column does not update the time.
However, we discovered looping is a better solution anyway. Thank you for your response though.

2 Likes
5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.