Forum

Hello, I have investigated the issue: your project is currently on the sjc1 shared cluster, which is being phased out. During the system's periodic checks (at 12:00 and 18:00), the account status check failed to correctly identify your Developer Plan trial subscription, causing the system to treat your service as a free plan and automatically pause it. This is an issue on the platform side, not an error on your part.

Your service has been restarted and should be working normally now. If it gets paused again, please reply directly to let us know, and we will restart it for you.

Recommendation: Since the sjc1 shared cluster is being phased out, we recommend migrating to a dedicated server for long-term stability. The most affordable plan is approximately $2–3/month (Tencent Cloud Hong Kong or Singapore). There is a one-click migration feature on the Dashboard that can automatically transfer your services, environment variables, and disk data. This will prevent any further issues with automatic suspension.

Hello, thank you for your assistance!

However, we are currently in a small-scale trial phase. If this happens frequently and requires you to restart, I am concerned it might cause you trouble.

We may need to monitor the frequency of this issue before considering a migration to a dedicated server.

If we haven't migrated to a dedicated server yet, will these disconnections continue to happen frequently?

Hello,

I have just confirmed with the engineering team that this bug has been fixed. The root cause of the issue where paid users (including Dev trial users) were incorrectly identified as free users and suspended has been resolved.

Please try restarting your n8n service. Once it starts up normally, it will no longer be automatically shut down every 12 hours.

If you continue to experience incorrect suspensions, please let us know, and we will immediately check the specific status of your account from the backend. We recommend keeping an eye on it tonight or tomorrow around 12:00 PM (the time when the issue previously occurred) to confirm that the fix is effective.

Regarding migrating to a dedicated server: There is no need to upgrade because of this bug. Once fixed, your current Dev plan + shared cluster setup will continue to work, and you do not need to spend extra money.

Hello, thank you for your help!

I would also like to ask, since I have been using the free traffic quota and just purchased more because I ran out this month, I will likely stick to the free tier in the future (as I am still in the trial and testing phase).

However, is there still a risk that my n8n instance will be suspended in the future due to being a free-tier user?

Thank you!

Hello,

Your current Developer Plan trial expires on 6/1. If you do not renew after the expiration date, your account will revert to the Free Plan.

Since your service is on a shared cluster, services under the Free Plan will be suspended and will not automatically restart. As n8n is a service that runs 24/7, it will be suspended under the Free Plan.

To ensure long-term stable use of n8n, we recommend:

1. Subscribing to the Developer Plan ($5/month) after the trial ends.
2. Or migrating to a dedicated server (VPS), which starts at approximately $2–3/month. This way, your service will not be restricted by the shared cluster and will not be automatically suspended.

Hello, we have purchased a server, but the following message appeared during the migration:

Failed Volume Copy: n8n failed - restore job failed 16:53:59

Failed Clone Failed: 1 volume copies failed 16:53:59

However, I can see that n8n is already present on the server. I am not sure if the copy was incomplete. Could you please help me check this? Thank you!

Hello,

We have checked the backend, and here is the conclusion: Your data is not lost; it has been fully copied to the new server.

Explanation:

1. Your 24 workflows and 12 sets of credentials are stored in the PostgreSQL database. This database has been successfully copied to the new server, and the content is identical to the original with no data missing.

2. The only part that failed to copy was the storage disk for the n8n service itself. This disk does not contain your workflows or credentials (those are in the database and have already been copied), nor does it affect the encryption keys (keys are stored in environment variables and are carried over). Therefore, this error message will not cause any data loss.

3. Reason for failure: System logs show that "Clone Project" was clicked twice, creating two identical projects. With two sets of databases running simultaneously on this 2GB RAM server, the memory was insufficient, causing the n8n disk copy task to time out.

Please perform the following action: You currently have two identical projects on your new server. Please keep one and delete the duplicate. Once deleted, memory will be freed up, and the n8n service should automatically start within a few minutes; your original workflows will be there.

If n8n remains stopped after deletion, please reply to us, and we will manually start the service for you from the backend.

Two additional reminders:

• It is recommended to keep the original n8n project for now and delete it only after confirming that the new server is working properly.
• Running both n8n and the database on 2GB of RAM is quite tight. If you experience slowness or automatic restarts in the future, you may want to consider upgrading your server specifications.