n8n Execution Logs Continuously Loading on VPS

Below is some guidance that can help troubleshoot the issue:

Check for Memory Limitations

When viewing logs, especially from workflows that process large data or many nodes, n8n needs to load all that data into memory. On VPS setups this can push the available memory limits. In some cases, if the memory isn’t sufficient the log view might hang.

1. Review Server Logs: Look for error messages like "Allocation failed - JavaScript heap out of memory". Such messages indicate that n8n is running out of memory when trying to load the log data.

2. Increase Available Memory:

   • If you’re self-hosting on a VPS, consider increasing the memory provision for the n8n instance.
   • You may also allocate additional memory to the Node.js process by using the V8 option (e.g., setting --max-old-space-size=SIZE either via CLI or the NODE_OPTIONS environment variable).

3. Reduce Memory Consumption:
   If increasing memory isn’t an option, you might want to reduce the amount of data processed by your workflows. This could involve:

   • Optimizing workflows so that nodes aren’t handling more data than necessary.
   • Reducing the number of nodes or the size of JSON data that’s being processed.

Next Steps

• Restart n8n:
  If you see memory errors in your server logs, note that while n8n Cloud and Docker setups auto-restart n8n on such errors, if you’re running n8n using npm you might need to restart it manually after making adjustments.

• Monitor VPS Resources:
  Ensure that the VPS resources (especially available RAM) are adequate for the workflow executions, particularly if you’re running multiple workflows concurrently.

Following these steps should help resolve the issue with execution logs not loading due to memory constraints. Let us know if you need more assistance!