Hey Guys I am having an issue here, my workflows keeps on duplicating the results though my action are clear and correct. I have an if statement that checks if an appointment is created, rescheduled or canceled, sometimes when the trigger is reschedule the workflow doesnt use the correct breanch instead it creates the appointment.
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 @Anga_Matsuluka,
Can you share the actual worklfow and an execution run that shows the issue, Looking at your screenshot I can’t see anything wrong so it would be handy to see where it is duplicating then being able to also see that data if possible so we can work out what is going on.
The workflow has some confidential API keys, so I am not sure how I can share it without giving you the credentials. Let me try to explain the problem a bit more, The workflow works fine but it has a problem of duplicating the appointments that its creating, Sometimes when I run it it doesnt create any duplicates but sometimes when the rescheduled or canceled trigger the flow goes to the first part which is creating a duplicate. I have 3 if statements that check the status from a webhook. If the webhook status is catch-all, then take the first flow, if the status is reschedule, take the second flow to the third flow.
This is the first if
This is the second if
this is the third if
Hey @Anga_Matsuluka,
Based on your screenshots I really can’t see an issue, What I would do though is if you are using the data from the Webhook node I would use the newer $('Webhook').item.json.query.status syntax but as the webhook will only be called once I would use $('Webhook').first().json.query.status.
Other than that I would need to see the execution view of a failure and the data to work out what is going on.
Thank you, I am confused because I see nothing wrong as well and I am not getting any failure
Hey @Anga_Matsuluka,
If you can share the info asked for we can look into it further.
Where can I share
Here… We just need a screenshot of the execution that failed and the data that didn’t work. This is likely to be a workflow design issue rather than an n8n issue so it may take a while to get to the bottom if it.
The issue is that the execution doesnt fail its just that the workflow creates duplicates
Now I need a way to remove the dupliactes
Hey @Anga_Matsuluka,
If it is creating duplicates I would see that as a failure which is why I have been referring to it as a failure / error.
If you can share the information requested I am sure we can work something out but chances are this will be down to the workflow logic so you may need to tweak that and put in a check for existing events.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.