Hi n8n team,
I’m encountering an unusual issue where a workflow failed due to a directory check, even though the directory does exist.
Issue Summary:
- The workflow reached a step where it checks if a specific directory exists.
- It determined that the directory does not exist and stopped further execution.
- However, when I manually inspected the system right after, the directory was present, and it contained three files — which matches the number of successful workflow executions.
- I also double-checked the command/logic used to check for the directory existence, and it’s working fine outside n8n.
- Additionally, when I accessed the server via shell, the directory was clearly present.
Why this is concerning:
This behavior seems abnormal on n8n’s side — there’s no clear reason why the directory check should have failed, given the presence and accuracy of the directory and command. It appears to be a potential timing or internal bug within the platform.
Supporting Material:
Please refer to the attached screenshots for more insights on:
- The failed execution and condition node
- Shell output showing the existing directory and its contents
- Workflow overview
Error it produced in original run:
On re-run:
Verification of the file via shell:
Let me know if any additional logs or debug info are needed.
Thanks,
Shubham