Schedule Trigger not triggering

Questions
1

Hi All,

Just updated to 1.57.0 on a self hosted vultr install. Have date time set in environment variables and set in the workflow, but the schedule trigger does no seem to work as expected. For example I have one flow set to trigger every 2 mins, but it did not trigger. I changed it to 1 min and it tirggered a few times and then stopped. Is anyone else seeing issues please? Thank you Paul

Debug info

core

  • n8nVersion: 1.57.0
  • platform: npm
  • nodeJsVersion: 18.19.0
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: community
  • consumerId: unknown

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

Generated at: 2024-09-11T12:17:33.683Z

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
5

Hey @paul2000 ,

You mentioned that this started to happen after the upgrade. Could you try upgrading yet again. The latest now is 1.59.3 in case it is specific to this version.

Could you tell us what ENV options you have set and with what values?

As a side note, would it be possible to switch to Docker instead of npm and see if that resolves the issue?

6

Hi ihortom,

Updated to 1.59.4 today and had the same issue. Restored back to version 1.44.1 to get working again.

I am running using npm on a debian dedicated vultr server. I also have n8n running on Yunohost and the crons are running fine on that one which is running n8n 1.56.2.

To get working on Yunohost I fed the error log into chat gpt and it said to add N8N_PROXY_TRUST=true and N8N_USE_PROXY=true to the .env I did this and the workflows started to trigger again. I also had to update a line in the nginx config.

The error log was not showing the same on the dedicated vultr server and I am not using a proxy either on that one so I did not try the same fix.

I will have to have another go another day. Sorry to be vague.

Thank you!

7

Thanks @paul2000 for sharing these discoveries! Keep us posted.

8

Just to close this issue. I could not get it sorted out. I think it may have been an issue unique to my install on Yunohost. I have now moved my workflows to a docker container install of n8n and all my workflows are working as expects and the crons / schedule are working as expects.

1 Like
9

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