503 - workspace offline - 13 hours plus zero updates

Questions
1

Describe the problem/error/question

Checked on executions this AM. Seven executions stuck in progress (starting around 6:30am EST) for over an hour with the following error:\ \ Problem saving workflow Autosave failed: SQLITE_IOERR: disk I/O error Retrying in 32s…\ \ Autosave also not working.\ \ Tried to stop all seven executions. Unsuccessful. Saw that I was due for a version update. Thought that might be the problem. Went to admin panel. Was currently running version 2.9.3. Selected 2.9.4. Then THAT became stuck IN PROGRESS and I was unable to open instance kalshinator5000. COMPLETELY LOCKED OUT. My account is cloud based, so whatever server issues there may be I would assume are happening on your end.\ \ Around 10:00am the instance status changed from IN PROGRESS to OFFLINE\ \ I tried to RESTART WORKSPACE but now it is stuck IN PROGRESS again.\ \ The AI assistant APPARENTLY forwarded this to the support team, but I have received ZERO feedback for OVER THIRTEEN HOURS. Obviously I need this back up and running. But, at THE VERY LEAST, I deserve SOMEONE giving me an update OR if no one is available there should be SOME SORT OF RESPONSE LETTING ME KNOW HOURS OF OPERATION.

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

This is a cloud infrastructure issue on n8n’s end, the SQLITE_IOERR thing has come up for other cloud users before and there’s nothing you can do from the admin panel to fix it, restarting just makes it worse honestly. You need the n8n team to unstick it from their backend. Email [email protected] directly if you haven’t already, their support hours are Berlin time (CET) Mon-Fri so depending on when you reached out there may have been a timezone gap. Frustrating situation for sure but this one is entirely on their infra side to resolve.

3

The SQLITE_IOERR thing on cloud is a server-side storage issue, nothing you did wrong and unfortunately nothing you can fix from your end either. This requires n8n support to intervene on the backend. Email [email protected] directly if you haven’t already, the AI chatbot forwarding stuff tends to be unreliable for urgent issues like this.

4

I definitely appreciate YOU taking the time to respond and provide some insight. Had I known that their support staff was not available until M-F I probably would have done something different with my day instead of refreshing my computer every 5 minutes. It’s unfortunate that neither their web site, ai helper-bot, autmoated email responses or admin panel provide this simple bit of information. I would have just been a patient but incredibly irritated customer instead of a profanity-laden rage monster throwing random office supplies at the wall.

Thanks again. Walking away, taking a breath, and looking forward to Monday resolution.

1 Like