Cheduled trigger not working, but Test executions complete fine

Questions
1

Describe the problem/error/question

I have installed N8N on a ProxMox LXC using the script available from Proxmox VE Helper-Scripts using the following command bash -c “$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/n8n.sh )”

I am able to run a RSS Feed Trigger only when selecting the Test workflow button. Otherwise I am not able to have it run on any selected schedule, even though it is active.

What is the error message (if any)?

I don’t see any errors, but also don’t know where to find any logs…

Please share your workflow

I

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.55.3
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Not set?
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system: Debian 12 (LXC)
1 Like
2

I do have it running behind a Traefik reverse proxy, but being that the site loads fine using the URL and that https functions as expected, I’d guess that’s not part of the problem.

3

Looking at the settings, it should be working. I wonder if it’s something with how n8n actually sets up the “cron” for these. Haven’t found any information on this in the docs.
image

Next up. Looking at the code… :crossed_fingers:

5

Was able to setup the logs and nothing seems out of the ordinary? It’s triggering, but not showing…

{"level":"verbose","message":"Updating versionId for workflow k5cAiFvn4Qivhof6 for user c4312751-5b30-4923-8eda-5dcd37ed7196 after saving","metadata":{"file":"workflow.service.js","function":"update","newVersionId":"dc36ae2c-b099-4ca4-9232-6abb0bd6d2c6","previousVersionId":"15e17127-0664-4dd3-a05c-c692a61951e5","timestamp":"2024-09-01T00:15:55.906Z"}} 
{"level":"warn","message":"Removed triggers and pollers for workflow \"k5cAiFvn4Qivhof6\"","metadata":{"file":"ActiveWorkflowManager.js","function":"removeWorkflowTriggersAndPollers","timestamp":"2024-09-01T00:15:55.909Z","workflowId":"k5cAiFvn4Qivhof6"}} 
{"level":"debug","message":"Adding triggers and pollers for workflow \"RSS update\" (ID: k5cAiFvn4Qivhof6)","metadata":{"file":"ActiveWorkflowManager.js","function":"addTriggersAndPollers","timestamp":"2024-09-01T00:15:55.920Z"}} 
{"level":"debug","message":"Polling trigger initiated for workflow \"RSS update\"","metadata":{"file":"LoggerProxy.js","function":"exports.debug","timestamp":"2024-09-01T00:15:55.920Z","workflowId":"k5cAiFvn4Qivhof6","workflowName":"RSS update"}} 
{"level":"verbose","message":"Workflow \"RSS update\" (ID: k5cAiFvn4Qivhof6) activated","metadata":{"file":"ActiveWorkflowManager.js","function":"addTriggersAndPollers","timestamp":"2024-09-01T00:15:56.488Z","workflowId":"k5cAiFvn4Qivhof6","workflowName":"RSS update"}} 
{"level":"debug","message":"Wait tracker querying database for waiting executions","metadata":{"file":"WaitTracker.js","function":"getWaitingExecutions","timestamp":"2024-09-01T00:16:23.546Z"}} 
{"level":"debug","message":"Wait tracker querying database for waiting executions","metadata":{"file":"WaitTracker.js","function":"getWaitingExecutions","timestamp":"2024-09-01T00:17:23.547Z"}} 
{"level":"debug","message":"Wait tracker querying database for waiting executions","metadata":{"file":"WaitTracker.js","function":"getWaitingExecutions","timestamp":"2024-09-01T00:18:23.547Z"}} 
{"level":"debug","message":"Wait tracker querying database for waiting executions","metadata":{"file":"WaitTracker.js","function":"getWaitingExecutions","timestamp":"2024-09-01T00:19:23.546Z"}} 
{"level":"debug","message":"Polling trigger initiated for workflow \"RSS update\"","metadata":{"file":"LoggerProxy.js","function":"exports.debug","timestamp":"2024-09-01T00:20:14.002Z","workflowId":"k5cAiFvn4Qivhof6","workflowName":"RSS update"}} 
{"level":"debug","message":"Wait tracker querying database for waiting executions","metadata":{"file":"WaitTracker.js","function":"getWaitingExecutions","timestamp":"2024-09-01T00:20:23.547Z"}}
8

Welcome to the community @ecotechie !

Tip for sharing information

Pasting your n8n workflow

Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.

```
<your workflow>
```

That implies to any JSON output you would like to share with us.

The trigger node is designed to get the latest data. The URL you provided contains the items with the newest publish date being June 27, 2024. When run in production mode the old items got skipped.

If you are interested in getting all the RSS items available you can try the following workflow.

9

Thanks for sharing that handy workflow. I’ll keep that in my back pocket. My interest with the one I created was to have the RSS Feed Trigger get the pubDate so I can compare it to the pub date of the last video I saw. If they don’t match, then I expect an email so I can go to the channel and watch the latest video.

I’m sure this can be done in a better fashion, but I’m just learning and “kicking the tires”. The issue I’m having is that the workflow just won’t run. The only way I have been able to get this to work is by hitting the Test workflow button. The “cron” does not seem to ever trigger. When it should be triggering every 10 minutes, right?

Thanks for any input you may have here…

10

The issue being that it never triggers. I am getting the data I want, the date of the latest item.

11

@ecotechie , it doesn’t trigger because there is no new (recent) items added to RSS feed. Have you tried any other feed that gets updated regularly?

1 Like
12

Hi @ecotechie
can you please help me how to fixed this issue

image
image1366×627 158 KB

2024-09-28T23:47:59.804Z | debug | [Pruning] Hard-deletion scheduled for next 15 min “{ file: ‘pruning.service.js’, function: ‘scheduleHardDeletion’ }”
2024-09-28T23:48:56.424Z | debug | Wait tracker querying database for waiting executions “{ file: ‘wait-tracker.js’, function: ‘getWaitingExecutions’ }”
2024-09-28T23:49:56.424Z | debug | Wait tracker querying database for waiting executions “{ file: ‘wait-tracker.js’, function: ‘getWaitingExecutions’ }”
2024-09-28T23:50:56.425Z | debug | Wait tracker querying database for waiting executions “{ file: ‘wait-tracker.js’, function: ‘getWaitingExecutions’ }”
2024-09-28T23:51:56.425Z | debug | Wait tracker querying database for waiting executions “{ file: ‘wait-tracker.js’, function: ‘getWaitingExecutions’ }”
2024-09-28T23:52:56.424Z | debug | Wait tracker querying database for waiting executions “{ file: ‘wait-tracker.js’, function: ‘getWaitingExecutions’ }”
2024-09-28T23:53:56.425Z | debug | Wait tracker querying database for waiting executions “{ file: ‘wait-tracker.js’, function: ‘getWaitingExecutions’ }”
2024-09-28T23:54:56.426Z | debug | Wait tracker querying database for waiting executions “{ file: ‘wait-tracker.js’, function: ‘getWaitingExecutions’ }”
2024-09-28T23:55:56.425Z | debug | Wait tracker querying database for waiting executions “{ file: ‘wait-tracker.js’, function: ‘getWaitingExecutions’ }”
2024-09-28T23:56:56.425Z | debug | Wait tracker querying database for waiting executions “{ file: ‘wait-tracker.js’, function: ‘getWaitingExecutions’ }”
2024-09-28T23:57:56.427Z | debug | Wait tracker querying database for waiting executions “{ file: ‘wait-tracker.js’, function: ‘getWaitingExecutions’ }”
2024-09-28T23:58:56.426Z | debug | Wait tracker querying database for waiting executions “{ file: ‘wait-tracker.js’, function: ‘getWaitingExecutions’ }”

I’m also facing the same issue.
FYI @Jon can you please help me with this.

13

Thanks @ihortom that was correct. It seems strange that the trigger doesn’t trigger if the link hasn’t been updated. I would had thought that it would have to trigger in order to know this in the first place.

I did update the link to a more active URL and, sure enough, it worked as hoped.

14

Hi, not really sure what your problem may be, but I’d suggest looking at the accepted solution. You may have the same issue I did.

Best of luck!

15

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