Understanding the instance queue

The instance queue controls when instances can start so the platform stays stable and fair for all users. This article explains why queues form, how they behave, and what you can do to reduce wait times and troubleshoot problems.

Why the queue exists

The queue protects system stability and performance by preventing more instances from starting than the platform can support. When demand exceeds available capacity, new instances are placed in a queue so running instances maintain predictable performance and resource contention is minimized. This preserves reliability for everyone on the platform.

How the queue works

• Capacity and demand: Instances are scheduled based on available compute capacity and current demand. When capacity is full, new start requests are ordered in the queue.
• Prioritization rules: The system may prioritize instances by plan type, region flexibility, or other policy settings. Priority rules determine which queued instances start first when capacity frees up.
• Position refresh: Queue positions are refreshed periodically. If the client stops refreshing—for example, if the browser tab is closed, the network connection drops, or no players remain connected—the instance may be removed from the queue to avoid reserving capacity for inactive requests. Keep the client or website open, or remain connected via auto-start on join, to maintain your queue position.
• Auto-start behavior: If you use auto-start on join, the platform keeps your queue position active while players remain connected. If no players connect, the instance may be dropped from the queue.

How to reduce queue times

• Choose a different region: Running your instance in a region that is currently less busy (often during off‑peak hours) can shorten wait times. Keep in mind this may increase latency during gameplay.
• Disable restricted scheduling: Allowing your instance to run in other regions increases flexibility and reduces queue delays. You can adjust this setting by editing the region.
• Upgrade to a paid plan: Paid plans include priority access, allowing your instance to skip the queue entirely.

FAQ

Why was my instance removed from the queue?

Queue positions are refreshed periodically. If your client stops refreshing—for example, if the browser is closed, the network connection drops, or no players remain connected—the system removes the instance from the queue to free capacity for active requests. To keep your queue position active, keep the website open when you start the instance from the site, or remain connected when using the auto-start on join feature.

The dashboard shows my instance started but players can’t join

Confirm the instance completed its startup sequence by checking server logs for errors. Common causes include failed plugins, missing assets, or configuration errors that prevent the server from accepting connections.

How long will I wait?

Wait times vary with global demand and available capacity. Changing region, enabling flexible scheduling, or upgrading to a priority plan are the most effective ways to reduce or eliminate waits.