Roblox Error Code 273: Duplicate Session, and What Triggers It
273 fires when Roblox detects two connections for one account. Multi-instance tools and background sessions are the usual causes.
The short answer
Roblox error code 273 means the platform detected a duplicate session for your account, usually from two clients running at once. Multi-instance tools and unclosed background clients are the most common triggers, and running multiple clients deliberately risks moderation action. Closing every Roblox process and rejoining resolves the genuine cases.
Verified and last updated August 12, 2026.
- Time needed
- 8 min
- Difficulty
- Beginner
- Read time
- 2 min
273 is Roblox telling you it can see two of you. Sometimes that is a crashed client that never let go, and sometimes it is a tool doing exactly what it was designed to do, which is the case worth worrying about.
After a crash, check Task Manager
A crashed Roblox client frequently leaves a process running that still holds the session. Your next launch is then a duplicate. This is the most common harmless cause.
Step 1: End every Roblox process
Clear leftover processes 2 minutes
Open Task Manager with Ctrl and Shift and Escape. Look under both Apps and Background processes for anything named Roblox, including the Roblox Player and the launcher. End each one. Then relaunch.
Do this before trying anything more involved. It resolves the majority of cases and takes under a minute.
Step 2: Stop using multi-instance tools
Tools that allow several Roblox clients to run simultaneously are the main deliberate cause of this error, and they are a poor trade.
Roblox's detection is specifically looking for this behaviour. Beyond the error, these tools are frequently classified as exploit software, and the moderation consequences run from a warning to account termination. The account bans guide covers what actually triggers enforcement across platforms.
Step 3: Log out of all sessions
If ending local processes does not help, the duplicate is elsewhere.
- Sign in on the Roblox website
- Settings, then Security
- Log out of all other sessions
- Sign back in on the device you want to use
What works
What doesn't
Key takeaways
Frequently asked questions
What is the difference between 264 and 273?
264 is specifically about joining an experience from a second device while already in one. 273 is a broader duplicate session detection that can fire from two clients on the same machine, including ones you did not realise were still running. In practice the remedies overlap heavily, and clearing all sessions resolves both.
Can I run two Roblox clients at once?
Not with a single account, and tools that enable it are the primary cause of this error. Beyond the error itself, multi-instance tools are frequently bundled with, or classified as, exploit software, and using them is a route to account moderation. The risk is disproportionate to the benefit.
Why does it happen after the game crashes?
Because a crashed client sometimes leaves a process running that still holds a session, so your next launch is detected as a duplicate. Ending the leftover process in Task Manager before relaunching fixes it. This is the most common innocent cause of 273.
Does this affect my account standing?
The error alone does not. Repeatedly triggering it through multi-instance tools might, because those tools are what Roblox's detection is looking for. An occasional 273 after a crash is unremarkable and carries no consequence.
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.