Roblox Error 280 means a script running inside the game exceeded the maximum allowed execution time and was killed by the Roblox engine. This is almost always a developer-side issue with an infinite loop or a very slow computation, not something you caused as a player.
Why it happens
Roblox's scripting engine enforces a maximum execution budget per script per frame. If a Lua script runs a tight loop without yielding (waiting), the engine detects the hang and forcibly disconnects affected players. Experience developers typically cause this accidentally during updates.
What to do as a player
You cannot fix a script timeout — it is the developer's responsibility. Wait 10–20 minutes and try rejoining. If the error persists across multiple sessions on the same experience, report it through the experience's page using the Report Abuse button.
How to fix step by step
- 1Wait 15–20 minutes before rejoining
- 2Try a different server using the server list on the experience page
- 3Report the issue to the experience developer via the Roblox game page
How 280 differs from related codes
- Error 517: Roblox returned an HTTP 517 or server-side error while loading an experience or API request. (server or client)
- Error 610: Roblox failed to load required assets for an experience or your avatar. (server or client)
- Error 524: Roblox received an invalid or timed-out HTTP response from its backend. (usually server-side)