Workflows that poll Notion failing and reporting "starting soon"

Questions
1

Describe the problem/error/question

Have several workflows that grab data from various notion databases, I have made sure to spread out their poll times so they don’t happen at the same time. But one of them I want to run more frequently, it often fails. I assume that is due to some kind of api limit or something.. that’s fine. My issue is on the ones that fail they all status=error and started=“starting soon”… forever. It makes no sense.

What is the error message (if any)?

The DNS server returned an error, perhaps the server is offline - thats the error from the notion lookups.
But my ticket is about why the ones that say error have started as “starting soon”

Please share your workflow

Not really required, its failing on the very first step (the notion lookup) and isn’t really relevant to my question.

Share the output returned by the last node

n/a

Information on your n8n setup

  • n8n version: 1.95.3 (but has been happening for ages)
  • Database (default: SQLite): SQlite
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker (runtipi)
  • Operating system: ubuntu
1 Like
2

Review the following:

  1. Check the status of the execution queue and see if there are many “pending” or “active” executions from the database or in the execution interface.

  2. Consider using an external database (PostgreSQL). For more demanding environments or those with frequent polling, SQLite is not suitable.

  3. Restart stuck processes, if possible, and clean up stuck executions manually from the UI or via SQLite with:

DELETE FROM execution_entity WHERE status = 'running';

3

Hey @Meisner

I had similar issue, the workflow was executing, even though I removed the trigger, it seems even though the workflow was different it was triggering from an old, to get around it as I didn’t want to spend hours debugging it, I just copied the workflow by duplicating it, and then didn’t see executions going off every second and fixed the errors I faced, but worth trying.

It seemed to me that the db had an issue telling it / referencing an old workflow hence why that trigger kept trying and got stuck in a loop.

Maybe trying in new workflow will help or a restart,

Samuel

Samuel

4

Hi @Erick_Torres,

Thank you for your response. Firstly my apologies I was mistaken, I checked the details for my n8n instance and it is indeed already running postgres not sqllite.

I have checked and nothing is still running, this is what i am referring to with the “starting soon” issue.

image
image1086×654 49.4 KB

Thanks,

5

Hi @King_Samuel_David

Thank you for that, I’m not sure it matches up to my issue and its not a single workflow that says “starting soon” if it errors. But if I i don’t find anything else i will try recreating them.

Thanks,

1 Like
6

Hey @Meisner

So, my guess it the trigger has issues, and maybe showing this state of starting soon, but errored likely when on the trigger hense no run time, and status.

Hope this helps,

Samuel