Roblox TeleportService Not Working in Studio? Test Teleports the Right Way

A teleport that does not run during a Roblox Studio playtest does not establish that your teleport code is broken. Roblox states that TeleportService does not support Studio playtesting; you must publish the game and test it in the Roblox client. (Teleport between places)

Prepare the client test

1. Publish the starting game with File > Publish to Roblox.
2. Publish the destination place. Roblox documents File > Publish to Roblox As…, followed by Add as a new place, as the workflow for adding another place to an existing game.
3. Copy the destination place's numeric PlaceId and use it as the first argument to TeleportAsync().
4. Launch the published game in the Roblox client and perform the teleport there.

A game with a Private audience is available only to its owner and users with Edit permission. Users who only have playtest permission need the audience set to Limited > Playtesters. (Create and publish games and places)

Call TeleportAsync from a server script

TeleportAsync() accepts a destination PlaceId, an array of Player instances, and an optional TeleportOptions instance. Roblox permits TeleportAsync() only from server scripts as a protection against client-side exploits. (Teleport between places, TeleportService API reference)

The following server-side diagnostic example protects the call, logs failures, and keeps retries bounded. Replace the placeholder ID, create a part named TeleportTestPad in Workspace, and place a ProximityPrompt inside that part.

local Players = game:GetService("Players")
local TeleportService = game:GetService("TeleportService")

local TARGET_PLACE_ID = 1234567890 -- Replace with the destination PlaceId
local ATTEMPT_LIMIT = 3
local RETRY_DELAY = 2
local FLOOD_DELAY = 15

local prompt = workspace.TeleportTestPad.ProximityPrompt
local attemptsByPlayer = {}

local function attemptTeleport(player, teleportOptions)
    if player.Parent ~= Players then
        return
    end

    local attempt = (attemptsByPlayer[player] or 0) + 1
    attemptsByPlayer[player] = attempt

    local success, result = pcall(function()
        return TeleportService:TeleportAsync(
            TARGET_PLACE_ID,
            { player },
            teleportOptions
        )
    end)

    if success then
        return
    end

    warn(("Teleport request failed for %s on attempt %d: %s")
        :format(player.Name, attempt, tostring(result)))

    if attempt < ATTEMPT_LIMIT then
        task.delay(RETRY_DELAY, function()
            attemptTeleport(player, teleportOptions)
        end)
    end
end

TeleportService.TeleportInitFailed:Connect(function(
    player,
    teleportResult,
    errorMessage,
    placeId,
    teleportOptions
)
    if placeId ~= TARGET_PLACE_ID then
        return
    end

    warn(("Teleport initialization failed for %s: %s — %s")
        :format(player.Name, teleportResult.Name, errorMessage))

    local retryDelay
    if teleportResult == Enum.TeleportResult.Flooded then
        retryDelay = FLOOD_DELAY
    elseif teleportResult == Enum.TeleportResult.Failure then
        retryDelay = RETRY_DELAY
    else
        return
    end

    if (attemptsByPlayer[player] or 0) >= ATTEMPT_LIMIT then
        warn(("Teleport retry limit reached for %s"):format(player.Name))
        return
    end

    task.delay(retryDelay, function()
        attemptTeleport(player, teleportOptions)
    end)
end)

prompt.Triggered:Connect(function(player)
    attemptsByPlayer[player] = 0
    attemptTeleport(player, nil)
end)

Players.PlayerRemoving:Connect(function(player)
    attemptsByPlayer[player] = nil
end)

The attempt limit and delays in this example are test settings, not Roblox requirements.

Capture both failure paths

Teleport calls involve network requests and can throw errors, so Roblox directs developers to wrap them in pcall(). A protected call can also succeed initially while the teleport later fails, leaves the player in the current server, and fires TeleportInitFailed. (Teleport between places)

TeleportInitFailed supplies the affected player, a TeleportResult, an error message, the original target place ID, and a TeleportOptions object populated with the information needed to retry the same destination. (TeleportService API reference)

Roblox's failure-handling example delays and retries Enum.TeleportResult.Flooded and Enum.TeleportResult.Failure; it reports other results as invalid teleports instead of retrying them. (Teleport between places)

Diagnostic checklist

• Publish the starting game and destination place.
• Pass the destination PlaceId to TeleportAsync().
• Run TeleportAsync() from a server script.
• Test through the Roblox client, not a Studio playtest.
• Record errors thrown by the call through pcall().
• Record later failures through TeleportInitFailed.
• Keep retries bounded and restrict automatic late-failure retries to the transient results handled by Roblox's example.