Here, I want to create a workflow using N8N nodes to:
- receive invitation in GCal > create event in Notion DB.
- event update in GCal > update in Notion.
- first is that the Google Calendar triggers for both creation and update (more often in the update case) do not always work, and this happens randomly. I’ve run multiple tests and noticed that the execution simply doesn’t execute sometimes (quiet often actualy), even though I’ve clearly received a new event invitation or an event has been updated.
- second issue is that sometimes, even if the execution starts, some branches of the workflow that are supposed to execute do indeed execute, but others that should also execute don’t (the ‘If’ condition is met, but the execution doesn’t proceed nonetheless).
- third issue (which doesn’t have major operational repercussions for me but I find strange nonetheless) is that when I receive a new event invitation and it works, not only does the “create” trigger activate, but the “update” trigger also activates immediately right after.
Overall, there is a significant issue with robustness, and I’m not sure how to fix it. Do you have any suggestions for solutions?
Here is my workflow with the double execution issue (the third issue) :
Now here is my workflow (anonymised & simplified to be under the character limit for posting a question ) :
Hi @sssamsss8 Thanks for so thoroughly going into detail about what you’re experiencing!
A few questions for you:
- Would it often be the case that perhaps the trigger is being fired multiple times in quick succession when you’re finding that the workflow isn’t executing?
- Could you provide an example of when the workflow didn’t follow the If condition that you expected? Example JSON data would be great!
- For the third, are you changing the calendar event in any way? The update trigger would be looking for any changes to events, so that could be causing it.
If you’re self-hosting n8n, would you also have any logs that you could share with us?
Finally, one more thing that would be useful to know:
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
I changed simplified the workflow spliting it into several ones and it is now working : The central branches with the “wait” in a workflow and the lateral branches in another workflow.
Hard for me to say why it is now working.
Thank you for your help anyway !
I spoke too quickly !
The problem remains for the notion update trigger part.
With the changes, as I was saying, I now have 2 workflows.
The problème is now on the 2nd workflow (the lateral branches).
I use un Notion create trigger and Notion update trigger to create or update data from a notion base to another notion base.
More precisely it is the update trigger that have issues. Indeed randomly it juste don’t trigger at all and the event is not in the executions panel.
Someting else I noticed is a lot of “status unknown” in the list of executions :
- **n8n version: 1.7.1
- Database (default: SQLite):
- **n8n EXECUTIONS_PROCESS setting (default: own, main): n8n cloud
- **Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
- **Operating system: Mac
Hi @sssamsss8 That issue with the Notion trigger you’re experiencing is going to be difficult to try to reproduce When it happens, are you sending a large amount of data to n8n, or would the trigger be hit numerous times? What polling times are you using, and what kind of edits are you doing to your database pages?
Hi @EmeraldHerald !
I am poling every min. But I can have an hour poling if it can solve the triggering problem.
I am not sending large amount of data to n8n at all.
How can I verify that the trigger is being hit numerous times or not ?
Thank you !