Roblox Error Code 274 Explained
274 is a scheduled shutdown, not a crash. The difference determines whether waiting helps.
The short answer
Roblox error code 274 indicates the server you were connected to was shut down deliberately, typically by the experience's developer publishing an update or clearing instances. It differs from a crash in that the shutdown is orderly and intentional, so player data saved before the shutdown is retained. Rejoining after a short pause places you on an updated instance.
Verified and last updated August 12, 2026.
- Time needed
- 6 min
- Difficulty
- Beginner
- Read time
- 2 min
Error 274 is a planned shutdown. A developer published an update, or cleared instances deliberately, and everyone on that server went with it.
The good news is that orderly shutdowns give the experience a chance to save your data first, which a crash does not.
Wait a minute before rejoining
Rejoining instantly frequently lands you on another instance already scheduled to close. Sixty seconds is usually enough for the new version to come up.
Step 1: Wait sixty seconds before rejoining
This is the whole fix in most cases, and it is the step people skip.
During a publish, shutdown propagates across instances over a minute or two. Joining during that window means joining something about to close, which produces 274 again and creates the impression of a persistent fault.
Step 2: Check whether an update just landed
If you rejoin and there is visibly new content, that confirms it: you were disconnected by an update and everything is working normally.
Hours of repeated 274 is a different matter, and worth raising in the experience's community. The 271 guide covers the closely related general disconnection code.
What works
What doesn't
Key takeaways
Frequently asked questions
Will I lose progress from a 274 shutdown?
Generally no, because an orderly shutdown gives the experience an opportunity to save player data before instances close, and well-built games use it. You may lose the last few moments of unsaved activity, such as items collected in the final seconds. This is meaningfully safer than a crash, where no save opportunity exists.
Why does rejoining immediately fail?
Because the shutdown is still propagating and you land on an instance already scheduled for closure. Waiting sixty seconds allows the new version to come up and lets you join a fresh instance. Immediately hammering the join button during a publish is the main reason people see 274 several times in a row.
Can I tell when a shutdown is coming?
Sometimes. Many experiences display an in-game countdown before a scheduled shutdown, giving players time to reach a safe point. Games without that courtesy simply close. If you play something that updates frequently, watching for the notice is worth the habit.
About the author
Roblox & Live-Service Editor
Priya started scripting in Roblox Studio at fourteen and has since published three experiences, the largest of which passed 1.2 million visits. That background is why our Roblox coverage explains why a code fails rather than just telling you to try again later.
Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.