Frequently Asked Question

Problem: Scheduled automated workflows fail to trigger at their specific time of day, or the system appears entirely offline.

Likely Cause: On Windows-based host environments, Windows Subsystem for Linux (WSL) or automatic Docker Desktop background updates can occasionally stall local container engines, requiring a manual system refresh.

Immediate Resolution Steps:

1. Trigger the Workflow Manually: You do not have to wait for the next scheduled daily cycle. Open your system's user dashboard or local n8n interface and click the "Run Workflow Manually" trigger button to immediately process backlogged folders.
2. Verify Docker Container Status: Open your Docker Desktop console or run docker ps in your terminal. Verify that the core automation, database, and OCR engine containers read as "Up/Running".
3. Restart the Stack via Terminal: If the containers are frozen or stalled due to a background WSL update, open your terminal as an Administrator and execute a clean restart:

Command Line Bash - wsl --shutdown

After executing the shutdown, relaunch your Docker Desktop application. This forces WSL to flush its virtual memory allocation and cleanly boots up your SQL Server, Postgres, and automation containers to a stable running state.