Issue: My n8n service project is consuming excessive memory (8GB+) and has crashed. The service is unable to restart, and my Postgres database is stuck in recovery mode.

Error Details:

- n8n service crashed due to memory exhaustion

- Postgres database shows "the database system is in recovery mode" and "not yet accepting connections"

- Service restart attempts fail due to memory constraints

- Railway CLI authentication issues preventing manual intervention

Root Cause:

- n8n workflow had an infinite loop

- This created endless processing that consumed all available memory

- The infinite loop has been identified and fixed in the workflow, but the service needs to be restarted.

Request:

- Need assistance restarting the n8n service to clear memory and stop the infinite loop

- Postgres database may need to be restarted as well to exit recovery mode

- Service should work normally once restarted with the corrected workflow

Services affected: n8n (Primary) and Postgres