Workflow execution had an error, but no error

Questions
1

Hello, this is the first time I encounter this problem.
My workflow throw this error on execution:

Workflow execution had an error
The workflow has issues and can for that reason not be executed. Please fix them first.

I’ve workflow A that run every 30 minutes.
Workflow A runs workflow B if a condition is met.

The problem is when my workflow B try to execute from the workflow A automatically (from the schedule node). Because when I manually launch workflow A, workflow B works perfectly.

When I open workflow B after an error, it doesn’t tell me what’s the problem.
No node with error, nothing. So I don’t know what to fix?

Can someone help here? I really don’t understand. Thanks!

Workflow A:

CleanShot 2024-08-02 at 10.09.03@2x
CleanShot 2024-08-02 at 10.09.03@2x1594×704 45.8 KB

Workflow B:

Share the output returned by the last node

Information on your n8n setup

  • **n8n version:**1.51.1
  • **Database (default: SQLite):**SQLite
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Own instance on Railway.
2

Here’s my workflow A for reference:

3

Hi @Theovogg

Thanks for reporting this!

Since you’re self-hosting, could you please share what you’re getting in the error logs?

5

Hello @ria thanks, what do you mean by error logs exactly?

6

Hi @Theovogg

You can set up error logging for n8n, which can be very helpful for debugging:

Also, are the executions being saved for both workflows?
What does it show in the executions tab for these?

7

Alright, I’ll setup this @ria.

Yes the executions are saved for both workflows.
Workflow A with no error.
Workflow B with this error:

Workflow execution had an error
The workflow has issues and can for that reason not be executed. Please fix them first

I recorded a super quick Loom video to show you:

9

Also, I just added N8N_LOG_LEVEL = debug and N8N_LOG_OUTPUT = console.

Here are all my console logs when I open the workflow B: Aug 02 12:44 PM - Codeshare.

I can see this error:

CleanShot 2024-08-02 at 14.42.41@2x
CleanShot 2024-08-02 at 14.42.41@2x1114×1382 204 KB

10

Up, please. I tried to solve this problem for 5+ hours.

11

Hi @Theovogg

sorry for the delayed response.

Could you try running the sub-workflow (Workflow B) with a Schedule Trigger and see if that executes it in production mode?

12

Hi @Theovogg

did you have any success? Would be interesting to know if you are still seeing this? Have you updated in the meantime?

Thanks for your feedback! :pray:

13

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