How to avoid "API service temporarily unavailable" error?

Questions
,
1

Is there any way of avoiding this error output every time the Notion public API is temporarily unavailable?
image

image
image430×676 33.6 KB

Of course I could create a filter in my Error Handler workflow, but I’d like to receive a warning when the service is genuinely down for a significant period.

However, I keep getting warnings even when everything appears to be working fine.

Information on your n8n setup

  • n8n version: 1.52.2
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: Ubuntu 22.04
2

Hi @gmsalomao2

I guess this means the notion trigger polls the data. So setting a retry in the node options might solve the issue. Never seen it before really so not sure if this would solve that.

3

The Notion triggers are indeed made of API polling.
But unfortunately there’s no “retry” setting available on them.

4

Just to be clear. I was talking about the general node settings that can be accessed by clicking on the cog icon.
Not sure if they would be there for trigger nodes, cannot check right now.

5

These here, right?
image

They don’t have the same settings as the HTTP request node:

image
image428×649 11 KB

6

Yep thats it. Learned something new today. I always thought it was there for everything.

Work around would be a schedule node and polling manually.

7

Yeah… thought of that too.

But this would totally dismiss the reason why Notion triggers exist and make me do it everything manually.

Last week I got about 8 error messages because Notion API was down for a few minutes.

I’ll keep this topic open so more people can contribute with their ideas.

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.