Hi, I set up a workflow triggered by new entry in Notion database.
When I test the workflow, everything is ok. Step by step, or the entire flow.
But, when workflow published, when a new entry (a new row in database) is created, the workflow does not start. I can’t see the run in the “runs” section. No success, no error…
How can you help please?
Hello @flagnico,
Something to note here, the trigger isn’t instant, so you might have to wait a few minutes for it to run. Do new entries not show even after a while?
Hi! I have similar problem.
Web panel prints that the flow should runs every 5 minutes
but flow doesn’t run (I can’t see the run in the “runs” section).
I use self hosted solution.
Hi there @swimmwatch welcome to our community 
Are you running the latest version of Activepieces ? and could you please make sure there are no errors in your terminal that’s running Activepieces ?
@Abdul yes, i use v0.15.0.
There are no errors in Activepieces Docker container.
@Abdul @MoShizzle I have noticed that the event “Update Database Item” emits when create new database item. If edit some database item (for example: change some property value) then event “Update Database Item” doesn’t emit.
All this runs were triggered by “Create Database Item” event:
I’m having the same issue. In looking at my logs it APPEARS that the notion hook is being executed when I make a change to my notion database. What else should I look at to troubleshoot?
2024-02-18 08:56:07 {"level":30,"time":1708271767524,"pid":8,"hostname":"d244183ce003","reqId":"req-fs","req":{"method":"GET","url":"/v1/worker/app-connections/notion?projectId=JnQPrzGxE2a123PZT2CFW","hostname":"127.0.0.1:3000","remoteAddress":"127.0.0.1","remotePort":42328},"msg":"incoming request"}
2024-02-18 08:56:07 {"level":30,"time":1708271767527,"pid":8,"hostname":"d244183ce003","reqId":"req-fs","res":{"statusCode":200},"responseTime":2.5827500000596046,"msg":"request completed"}
2024-02-18 08:56:10 {"level":30,"time":1708271769966,"pid":8,"hostname":"d244183ce003","msg":"sandbox, command: cd /usr/src/app/dist/packages/server/api/sandbox/0 && cross-env-shell AP_CODE_SANDBOX_TYPE=NO_OP AP_PIECES_SOURCE=CLOUD_AND_DB NODE_OPTIONS=--enable-source-maps \"/usr/local/bin/node\" main.js EXECUTE_TRIGGER_HOOK"}
2024-02-18 08:56:10 {"level":30,"time":1708271770499,"pid":8,"hostname":"d244183ce003","reqId":"req-ft","req":{"method":"GET","url":"/v1/worker/app-connections/notion?projectId=JnQPrzGxE2a123PZT2CFW","hostname":"127.0.0.1:3000","remoteAddress":"127.0.0.1","remotePort":42342},"msg":"incoming request"}
2024-02-18 08:56:10 {"level":30,"time":1708271770501,"pid":8,"hostname":"d244183ce003","reqId":"req-ft","res":{"statusCode":200},"responseTime":2.2836670000106096,"msg":"request completed"}
2024-02-18 08:56:10 {"level":30,"time":1708271770516,"pid":8,"hostname":"d244183ce003","reqId":"req-fu","req":{"method":"POST","url":"/v1/store-entries","hostname":"127.0.0.1:3000","remoteAddress":"127.0.0.1","remotePort":42348},"msg":"incoming request"}
This is still happening for me using cloud.activepieces
1-Trigger: new Notion DB Item
2- this new item is used in every subsequent step
Everything tests fine.
When live, it does not trigger
If I force a run, only the first step of the flow uses the new DB item, every other step is based on the previous DB item, so it is never correctly in sync.
This makes the entire run/flow irrelevant and incorrect because it is not based on the correct line item.
The only way to get the flow to successfully complete is to click into each step of the flow, in order, and hit retest before moving to the next step. It will not otherwise do this automatically using the correct updated DB item.
@APauto , The “New Notion DB Item” trigger is not instant — it may take 1–5 minutes to detect new items.
it doesn’t trigger at all when a new database item is added?
I created a couple of more tests, (in order to see if it was something else corrupt in the flow) and the test is running.
It appears to be set by default only to run only every five minutes. Is this as intended? Can it be altered?
You mentioned it may take 1-5 min. Will be good to know, as that timing would not work for anything needing to be more interactive (which is what I was building: user input triggers the flow and subsequent steps in the engagement).
Is it possible for the timing to be altered on this? It is a long wait for the trigger to output