@Scarerror_Team this is a cloud instance so you can’t restart it yourself, email [email protected] and they’ll bounce it for you. the heavy workflow probably ate all the memory and the container is stuck. while you wait you can hit the n8n API to disable that workflow so it doesn’t auto-trigger again when they restart it:
grab your API key from n8n settings > API, swap in your instance name and the workflow ID of the heavy one, run this from any other n8n instance or even a local one to kill it before support restarts yours.
ran into this a couple times — the API approach for disabling before restart is the right move, otherwise it just re-triggers immediately on restart. worth splitting heavy file-processing jobs into smaller batches going forward to avoid hitting the cloud memory ceiling again.