n8n
n8n copied to clipboard
n8n-io
[Notion] Attempt to fix Notion trigger polling strategy
There are a few complaints about the notion trigger so I thought I could try to propose something.
The existing strategy is using timings of the call in order to decide which records to process and that can be risky especially on a 1 minute poll since there could times where the poll firing doesn't happen or happen too late because of the server being too busy... Plus it was checking for the last process record id to decide if there was a need to process thing which can be really wrong in the update mode where an object can be modified at different times and should be reprocessed.
So here instead I'm using the date of the last processed record as reference and processing any record from after that time or (since Notion timestamps are only down to the minute) from the same minute but that I didn't save as processed. That may be one contentious point here: in the documentation it is explicitly said to keep the static data to a minimum and here I'm saving an array of ids which is unpredictable in terms of size so I capped it to 10.
@knshiro really cool. Thanks for the contribution. I will have a look at this somewhere this week.
Hello @knshiro , thank you for your contribution, I had to add some fixes as request was failing probably due to API changes
Hi, any update on this? since the problen still exist when i tried the apps
Hi team, any updates on this? I'm also facing this problem. Apparently, Notion Trigger is still not usable.
Just picked this up again. I will do more testing this week and, if all is good, merge.
Is there any progress here? Really would love to be able to use polling again.
