N8n sends different data than shown in the preview

Hello, I have a very weird issue with the behavior of my workflow. I have a workflow to sync calendar events between two systems.

Within the loop that creates the events, I have an HTTP node writing back the synced event ID to my 2nd system. In the screenshots, we can see that the IDs are both different. However, the data being sent doesn’t reflect the preview in the workflow. When I check back in my 2nd system (the one we write back to with the HTTP node), the google_calendar_event_id is the same for both items!
image
image

Item 1, and it’s corresponding entry in the 2nd system.

image
image

Item 2, and it’s corresponding entry in the 2nd system.

This means that n8n is sending the same item for a different index within a loop. This makes the loop essentially useless and my data unreliable. Any clues?

Information on your n8n setup

  • 1.64.3
  • Docker

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

Hey @Loan_J,

Which node is adding the data twice and what does the data look like going into the Loop node? If you can give us some JSON data we can use to run the workflow we can try and reproduce it.

The node Write back created event to Odoo Calendar event is the one that receives the same data twice. In the preview, it shows different data for both items, but when checking the actual items in the database, they received the same data.

Solved the issue. After further investigation, I found out that the issue actually comes from my system.

1 Like

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