Hello,
my n8n cloud workspace seems to be internally locked.
I receive the following errors:
- “Timeout waiting for lock SQLiteWriteConnectionMutex to become available”
- “Workflow with ID not found”
The issue affects the entire workspace:
- workflows cannot be saved
- triggers cannot be disabled
- even completely new empty workflows fail
I already tried:
- logout/login
- restarting the browser
- waiting several minutes
- testing with new empty workflows
Could someone please check whether my cloud instance is stuck or corrupted and restart/clear any internal locks or executions?
Thank you very much.
This does sound like it is on the Cloud workspace side rather than a browser/session issue, especially since new empty workflows and trigger changes are failing too.
I would open a support ticket with the workspace URL, exact timestamps, and both errors: Timeout waiting for lock SQLiteWriteConnectionMutex to become available and Workflow with ID not found. Community members probably cannot clear the internal lock from here, but support should be able to check stuck executions/instance state.
One thing worth doing in the meantime is try not to keep retrying saves or toggling triggers. The instance is already in a bad state, and repeated attempts tend to pile up more failed operations that support then has to sort through.
Hopefully they get you unblocked quickly, this kind of thing is usually fixable on their end once they take a look.
Hi @Joern_Oschatz
Your n8n account is essentially “frozen” because its internal database has a stuck lock. Imagine a digital door that only one person can enter at a time; right now, a crashed process is standing in the doorway and won’t move. This is why you can’t save anything, change settings, or even create new workflows—the system is waiting for that “door” to open, but it never does.
Because this problem is happening on n8n’s servers and not in your browser, things like logging out or restarting your computer won’t help. Only the n8n technical team can go “behind the scenes” to force the lock open and restart your instance. You need to email help@n8n.io with your instance URL and the error messages so they can manually unfreeze your account.