Cool, btw since this is a built-in trigger, we don’t charge credits for executions, only for emitted events. So feel free to reduce the timer interval even more if you need the trigger to react quickly to changes!
I will check if the interval also works.
And yes, please let me know
Its now not working anymore. both trigger did not react time based on a change and now also “run now” doesn’t work again
OK thanks, I’ll ask the engineering team to investigate this
thank you
Oh actually there are errors in the logs
ah, I hope that’s “good” for resolving 
Am I looking at the correct trigger?
Oh no I wasn’t
It’s this one yeah?
its this:
and this:
Posted thread to Discourse: https://pipedream.com/community/t/undefined/undefined
Since I have to get this workflow running I tried today to duplicate the workflow and set up a new trigger. but the same problem occurs, the trigger does not fire, but the trigger log has errors: Sign Up - Pipedream
I see the Maximum execution time reached error in the logs, it indicates your Notion database is too large for processing. I would recommend you split the database (reduce the number of rows) if possible, or use another app. If you have access to Notion webhooks and automations, that would be the best approach
Hi thank you for the response. Since other trigger of the same style work one question: would it help to reduce the properties in this trigger or is it only the size of the notion database?
Depending on the property and what data it holds, it can help
But what would mostly help is to reduce the size of the database
Hi I played around a little bit, because I wonder, why my Database wit 200 entries could be to big and splitting would be a huge effort.
I also tried to trigger the workflow with a notion automation (property edited) but the notion automation fires not on finishing an edit (=leaving the field) but fires on every keystroke (3 sec pause) - so this is useless.
Do you have any other suggestions or tipp?