Execute command node never completes

Questions
1

Hello,

I added a custom binary/command to my n8n docker container called fabric (GitHub - danielmiessler/fabric: fabric is an open-source framework for augmenting humans using AI. It provides a modular framework for solving specific problems using a crowdsourced set of AI prompts that can be used anywhere.). I’ve verified that it works by connecting to the shell and testing it out, however, when I try to run even basic fabric commands (like fabric --version), the execute command node just spins and never completes. There re no apparent errors because the node doesn’t complete execution, nor does it error out.

My workflow, so far, is just a manual trigger followed by a execute command node.

I am running n8n v1.61.0 via Docker.

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

Hey @dmoore44,

If you enable execution logging and test it again does it show in the log as finished?

4

Dumb question… but how would I enable execution logging?

5

It is under the workflow settings on the top right.

6

It doesn’t look like any workflow logs have been generated… I left an execution running when I left the house earlier this morning, so I’ll check when I get home tonight and provide some screenshots.

7

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