The execution was aborted before starting - Reason?

Questions
1

Hello,

We’ve our own n8n instance hosted on Railway.
We have a few advanced workflows running everyday.
One of our workflows started to error all executions and N8N don’t display error message except : Problem with retry : The execution was aborted before starting, so it cannot be retried.

We didn’t change the workflow and it worked perfectly for weeks with 0 errors.
Do you know why? How can I solve the problem?

Here’s the full workflow code (too long): Oct 30 4:11 PM - Codeshare.
Quick Loom to show you: Arc - 🇫🇷 Terminator Pusher - 30 October 2024 | Loom.

Information on your n8n setup

  • n8n version: 1.64.3
  • Database (default: SQLite): sqlite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): hosted on railway
  • Operating system: macos
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:
3

Hello, up please.
I tried to fix the problem but still have the same errors.

4

Hey @Theovogg,

I would expect the retry to fail as there is no data to try and start the workflow with as is meant to be called from another workflow.

Why it suddenly stopped working though I am not sure, Have you checked the n8n logs to see if there are any error messages?

Did you make any changes at all like upgrade n8n?

5

Hello @Jon,

Alright I understand for the retry.
But as you can see the executions shows no errors, so I don’t understand what to fix.
I upgraded to the latest version of n8n but I’m not sure the problem happens at this moment.

What should I do next to solve the problem?

6

@Jon just checked my railway console.

my workflow tried to execute on Nov 04 around 20:00 and I can see that:

CleanShot 2024-11-05 at 11.17.19@2x
CleanShot 2024-11-05 at 11.17.19@2x1920×1072 197 KB

do you think it’s related?
is it related to this issue Execution log getting swamped with odd errors - #4 by jmls? i’m not sure how to fix the problem.